Code execution via unchecked compiler scope indexing
Published Dec 3, 2025 · Updated Dec 3, 2025
Heap buffer overflow in Pepper 0.1.1 and earlier allows local users to execute arbitrary code or crash the interpreter via a crafted .pr file. The add_constant function writes parsed numeric constants beyond the fixed 64-entry compiler.scopes array without enforcing its capacity. Execution of a source file containing at least 65 numeric constants triggers an out-of-bounds heap write in the Pepper process.
Summary
What happened
Heap buffer overflow in Pepper 0.1.1 and earlier allows local users to execute arbitrary code or crash the interpreter via a crafted .pr file. The add_constant function writes parsed numeric constants beyond the fixed 64-entry compiler.scopes array without enforcing its capacity. Execution of a source file containing at least 65 numeric constants triggers an out-of-bounds heap write in the Pepper process.
The record
- CVE
- CVE-2025-50360
- Published
- Dec 3, 2025
- Updated
- Dec 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-122, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 3, 2025CVE publishedPublication date reported by the CVE source.
- Dec 3, 2025Record 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.
Public exploit references
- 65-number Pepper source proof of conceptproof 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