Local process crash via format-specifier overflow
Published May 11, 2026 · Updated May 11, 2026
Stack buffer overflow in Squirrel 3.0 through 3.2 allows local users to crash the runtime via a crafted string format specifier. validate_format accepts a 20-character specifier because its limit check uses > instead of >=, then memcpy writes 21 bytes into fmt[1] of a 20-byte stack buffer. Exploitation requires local script execution with the string library; the demonstrated result is a runtime abort, while adjacent stack data can be corrupted.
Summary
What happened
Stack buffer overflow in Squirrel 3.0 through 3.2 allows local users to crash the runtime via a crafted string format specifier. validate_format accepts a 20-character specifier because its limit check uses > instead of >=, then memcpy writes 21 bytes into fmt[1] of a 20-byte stack buffer. Exploitation requires local script execution with the string library; the demonstrated result is a runtime abort, while adjacent stack data can be corrupted.
The record
- CVE
- CVE-2026-8258
- Published
- May 11, 2026
- Updated
- May 11, 2026
- Vendor
- Squirrel
- Product
- Squirrel
- Classifications
- CWE-119, CWE-121, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 11, 2026CVE publishedPublication date reported by the CVE source.
- May 11, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.0
- Affected versionversion=3.1
- Affected versionversion=3.2
What conditions does exploitation require?
What is affected?
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_format_stack_bof.nutproof 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