cve.bz

CVE-2026-112054 schroedinger schroedinger: Divide By Zero

6.8 mediumEPSS 0.2%

Medium (6.8) in schroedinger schroedinger. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
Schroedinger libschroedinger through 1.0.11 contains a divide by zero vulnerability that allows attackers to crash applications by supplying a zero slice_bytes_denom or slice count in a Dirac stream. Attackers can provide a crafted low-delay picture parsed by schro_decoder_parse_transform_parameters and schro_decoder_parse_lowdelay_transform_data to trigger a SIGFPE and cause denial of service.

Severity

CVSS 4.0

6.8 medium
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 8th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-10-22. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-369 Divide By Zero
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-112054 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-112054?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-112054?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-112054 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
schroedingerthrough 1.0.11

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu14.04:LTS, 16.04:LTSschroedingerno fix listedUBUNTU-CVE-2026-112054

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A divide-by-zero flaw was found in libschroedinger's low-delay Dirac transform parsing. A crafted Dirac stream with a zero slice_bytes_denom or zero slice count reaches an unguarded integer division (schrodecoder.c:2932 and schrolowdelay.c sinks), causing a SIGFPE application crash (denial of service). User interaction is required to process an attacker-supplied stream; the upstream project has been abandoned since 2012 and no fixed release exists.

Red Hat's mitigation

Avoid decoding untrusted Dirac streams with applications linked against libschroedinger. The Fedora/EPEL schroedinger package ships the unpatched upstream 1.0.11; upstream is abandoned, so remediation requires a downstream patch (reject zero slice_bytes_denom / n_horiz_slices / n_vert_slices, as proposed in the researcher writeup) or package retirement.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-112054.

References

Check your stackJSON