# CVE-2026-95958: JusticeRage Manalyze PE Parser pe.cpp _parse_relocations integer underflow

> An integer underflow in the Manalyze PE parser allows local attackers to cause a denial of service via manipulated block sizes.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-33f8-hqvp-cf7j

## What is CVE-2026-95958?

CVE-2026-95958 is a medium-severity vulnerability in JusticeRage Manalyze, published on 23 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A security flaw has been discovered in JusticeRage Manalyze 1.0.0. Impacted is the function PE::_parse_relocations of the file manape/pe.cpp of the component PE Parser. Performing a manipulation of the argument BlockSize results in integer underflow. The attack requires a local approach. The patch is named c372b6bbca9d8c63812be50596fefa4a79c65fd0. It is recommended to apply a patch to fix this issue.

Weakness: CWE-191 (Integer Underflow (Wrap or Wraparound)), CWE-189

## Which versions are affected by CVE-2026-95958?


## How do I fix CVE-2026-95958?

No fix has been published for CVE-2026-95958 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-95958 being exploited?

There is no known exploitation of CVE-2026-95958 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-95958 and fix it if it is affected.

What it is: CVE-2026-95958 is a medium-severity vulnerability in JusticeRage Manalyze, published on 23 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-95958 in the wild and no public exploit code.

Affected product: JusticeRage Manalyze. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-95958/ (Markdown: https://insights.sbomify.com/CVE-2026-95958/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-95958
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-95958
- OSV: https://osv.dev/vulnerability/CVE-2026-95958

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-95958/
Summaries are generated and may contain mistakes; the official description above is the record.