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.
CVE-2026-95958
Score 3.3 from GitHub Security Advisory published 2026-09-23. a secondary CVSS source baseline 3.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 3.3
- EG Score
- 3.3(high)
- EG Risk
- 15(Track)EG Risk 15/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity33% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 6%
- KEV
- Not listed
Published
September 23, 2026
Last Modified
September 23, 2026
References (6)
- cna@vuldbhttps://github.com/JusticeRage/Manalyze/
- cna@vuldbhttps://github.com/JusticeRage/Manalyze/commit/c372b6bbca9d8c63812be50596fefa4a79c65fd0
- cna@vuldbhttps://vuldb.com/cve/CVE-2026-95958
- cna@vuldbhttps://vuldb.com/submit/953395
- cna@vuldbhttps://vuldb.com/vuln/408568
- cna@vuldbhttps://vuldb.com/vuln/408568/cti
Vendor Advisories for CVE-2026-95958(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-23 18:20 UTCEG score recompute
- 2026-09-23 18:20 UTCGHSA enrichment
- 2026-09-23 17:54 UTCEG score recompute
- 2026-09-23 17:54 UTCGHSA enrichment
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-23 15:17 UTCEG score recompute
- 2026-09-23 15:17 UTCGHSA enrichment
- 2026-09-23 03:27 UTCEG score recompute
- 2026-09-23 02:53 UTCEG score recompute
- 2026-09-23 02:52 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-189 · CWE-191
Frequently asked(5)
What is CVE-2026-95958?
When was CVE-2026-95958 disclosed?
Is CVE-2026-95958 actively exploited?
What is the CVSS score of CVE-2026-95958?
How do I remediate CVE-2026-95958?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-95958
Is Your Infrastructure Affected by CVE-2026-95958?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.