Process interruption via pre-buffer null-byte write
Published Sep 9, 2026 · Updated Sep 9, 2026
Memory corruption in Nothings stb commit 31c1ad3 allows local users to interrupt an embedding process through a crafted call. In stbsp_vsnprintf, a nonpositive count makes the terminator index negative, causing a null byte to be written before the caller-provided buffer. The trigger requires code that passes an attacker-influenced count to the formatting API; the public report demonstrates memory corruption but no specific crash path.
Summary
What happened
Memory corruption in Nothings stb commit 31c1ad3 allows local users to interrupt an embedding process through a crafted call. In stbsp_vsnprintf, a nonpositive count makes the terminator index negative, causing a null byte to be written before the caller-provided buffer. The trigger requires code that passes an attacker-influenced count to the formatting API; the public report demonstrates memory corruption but no specific crash path.
The record
- CVE
- CVE-2026-79516
- Published
- Sep 9, 2026
- Updated
- Sep 9, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 9, 2026CVE publishedPublication date reported by the CVE source.
- Sep 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- poc_sprintf.c reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo