CVE-2026-112007 schismtracker CVE debrief

Who should care

Defenders responsible for systems or applications using Schism Tracker should assess exposure and prioritize verification and patching to prevent potential application crashes. This includes reviewing the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. Defenders should also plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Why it matters

This vulnerability in Schism Tracker can lead to application crashes and requires verification and potential patching to mitigate.

• Potential application crashes due to exploitation of this vulnerability
• Need for verification of Schism Tracker version in use
• Prioritization of patching or updating to a fixed version

Technical summary

The fmt_ult_load_song() function in fmt/ult.c fails to clamp the one-byte sample count to MAX_SAMPLES, allowing for a heap out-of-bounds write vulnerability. This can be exploited by supplying a crafted .ult module. The vulnerability affects Schism Tracker through version 20260524 and has a CVSS score of 6.9. Defenders should prioritize verifying the version of Schism Tracker in use and applying patches or updates as available to prevent potential crashes due to this vulnerability. The vulnerability is considered MEDIUM severity.

Defensive priority

Defenders should prioritize verifying the version of Schism Tracker in use and applying patches or updates as available to prevent potential crashes due to this vulnerability.

Recommended defensive actions

• Verify the version of Schism Tracker in use
• Apply patches or updates as available
• Monitor for potential crashes or anomalies in the application
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description and CVSS score. Additional information is available in source references, including GitHub and VulnCheck advisories. The vulnerability was disclosed on 2026-10-18T12:17:13.097Z and has not been modified since then. There are no known ransomware campaigns using this vulnerability. The CVE Program record and NVD detail page provide official information on the vulnerability.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.