Unspecified impact via relocation BlockSize underflow
Published Sep 23, 2026 · Updated Sep 23, 2026
Integer underflow in the PE parser in JusticeRage Manalyze 1.0.0 allows local users to cause unspecified impact via a crafted PE file. PE::_parse_relocations subtracts its eight-byte header size from an unchecked smaller BlockSize, wrapping the unsigned count that controls relocation-entry parsing. Exploitation requires local submission of a malformed PE file for analysis; the available records do not specify the resulting impact.
Summary
What happened
Integer underflow in the PE parser in JusticeRage Manalyze 1.0.0 allows local users to cause unspecified impact via a crafted PE file. PE::_parse_relocations subtracts its eight-byte header size from an unchecked smaller BlockSize, wrapping the unsigned count that controls relocation-entry parsing. Exploitation requires local submission of a malformed PE file for analysis; the available records do not specify the resulting impact.
The record
- CVE
- CVE-2026-95958
- Published
- Sep 23, 2026
- Updated
- Sep 23, 2026
- Vendor
- JusticeRage
- Product
- Manalyze
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 23, 2026CVE publishedPublication date reported by the CVE source.
- Sep 23, 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=1.0.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started