A security flaw has been discovered in JusticeRage Manalyze 1.0.0. The affected element is the function PE::_parse_debug of the file manape/pe.cpp of the component PE Parser. The manipulation of the argument misc.Length results in integer underflow. The attack may be performed from remote. The patch is identified as 3e299685759f4f767088871de58c5d07f98ee382. A patch should be applied to remediate this issue.
CVE-2026-94090
Score 6.3 from GitHub Security Advisory published 2026-09-21. a secondary CVSS source baseline 6.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
- 6.3
- EG Score
- 6.3(high)
- EG Risk
- 28(Track)EG Risk 28/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 computedSeverity63% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 24%
- KEV
- Not listed
Published
September 20, 2026
Last Modified
September 21, 2026
Advisory Details (2)
Auto-updated Sep 20, 2026GitHub - JusticeRage/Manalyze: A static analyzer for PE executables. · GitHub
https://github.com/JusticeRage/Manalyze/commit 3e299685759f (JusticeRage/Manalyze)
Fix landed in JusticeRage/Manalyze commit 3e299685759f — awaiting tagged release
https://github.com/JusticeRage/Manalyze/commit/3e299685759f4f767088871de58c5d07f98ee382Vendor Advisories for CVE-2026-94090(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 16× in last 7d / 16× 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 23:26 UTCEG score recompute
- 2026-09-23 23:26 UTCGHSA enrichment
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-22 21:53 UTCEG score recompute
- 2026-09-22 21:53 UTCGHSA enrichment
- 2026-09-22 16:01 UTCEPSS rescore
- 2026-09-21 21:09 UTCEPSS rescore
- 2026-09-21 20:21 UTCEG score recompute
- 2026-09-21 20:21 UTCGHSA enrichment
- 2026-09-21 19:55 UTCEG score recompute
- 2026-09-21 19:55 UTCGHSA enrichment
- 2026-09-21 13:40 UTCEG score recompute
- 2026-09-21 13:40 UTCGHSA enrichment
- 2026-09-20 22:27 UTCEG score recompute
- 2026-09-20 22:12 UTCEG score recompute
- 2026-09-20 22:11 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-189 · CWE-191
Frequently asked(5)
What is CVE-2026-94090?
When was CVE-2026-94090 disclosed?
Is CVE-2026-94090 actively exploited?
What is the CVSS score of CVE-2026-94090?
How do I remediate CVE-2026-94090?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-94090
Is Your Infrastructure Affected by CVE-2026-94090?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.