CVE-2026-94114

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 5.9 from GitHub Security Advisory (severity: HIGH) published 2026-10-06. A secondary CVSS source baseline 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-93970 (ENISA EUVD) · GHSA-2p8h-ph4h-rm2f (GitHub Security Advisories)Source: ENISA EUVD

5.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Symbolic name not mapping to correct class.

BCEL caches attacker-controlled classes under their self-declared names without validating the requested name, allowing subsequent lookups and name-keyed verification results to refer to a different class.

This issue affects Apache Commons BCEL: before 6.13.0.

Users are recommended to upgrade to version 6.13.0, which fixes the issue.

CVSS v3
5.9
EG Score
5.9MEDIUMmedium confidence
EG Risk
27
EG Risk 27/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity59% × 45%
Impact severity (EG Severity): CVSS 5.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
20th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.9): severity, escalated by confirmed exploitation. This CVE's 5.9 is its impact severity (EG Severity), not escalated.

EG Severity
5.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 6, 2026

Last Modified

October 8, 2026

Vendor Advisories for CVE-2026-94114(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
bcel6.10.0-1, 6.13.0-1, 6.5.0-2
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
bcel6.10.0-1, 6.13.0-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
bcel6.10.0-1
  • every version up to 6.13.0-1: fixed in 6.13.0-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 34× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  2. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  3. 2026-11-11 08:15 UTCEchelonGraph re-scored
  4. 2026-11-11 08:15 UTCGHSA enrichmentGHSA-2p8h-ph4h-rm2f · GitHub severity HIGH · GitHub CVSS 5.9
  5. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  6. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  7. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  8. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  9. 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  10. 2026-11-05 21:37 UTCEchelonGraph re-scored
  11. 2026-11-05 21:37 UTCGHSA enrichmentGHSA-2p8h-ph4h-rm2f · GitHub severity HIGH · GitHub CVSS 5.9
  12. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  13. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  14. 2026-11-04 02:02 UTCEchelonGraph re-scored
  15. 2026-11-04 02:02 UTCGHSA enrichmentGHSA-2p8h-ph4h-rm2f · GitHub severity HIGH · GitHub CVSS 5.9
  16. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  17. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  18. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  19. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  20. 2026-10-29 17:09 UTCEchelonGraph re-scored
  21. 2026-10-29 17:09 UTCGHSA enrichmentGHSA-2p8h-ph4h-rm2f · GitHub severity HIGH · GitHub CVSS 5.9
  22. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  23. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  24. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  25. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
Show 47 more
  1. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  2. 2026-10-25 13:49 UTCEchelonGraph re-scored
  3. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  4. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  5. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  6. 2026-10-22 12:27 UTCEchelonGraph re-scored
  7. 2026-10-22 12:27 UTCGHSA enrichmentGHSA-2p8h-ph4h-rm2f · GitHub severity HIGH · GitHub CVSS 5.9
  8. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  9. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  10. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  11. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  12. 2026-10-18 02:58 UTCEchelonGraph re-scored
  13. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  14. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  15. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  16. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  17. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  18. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  19. 2026-10-12 14:42 UTCEchelonGraph re-scored
  20. 2026-10-12 01:28 UTCGHSA enrichmentGHSA-2p8h-ph4h-rm2f · GitHub severity HIGH · GitHub CVSS 5.9
  21. 2026-10-11 19:12 UTCEchelonGraph re-scored
  22. 2026-10-11 16:27 UTCEchelonGraph re-scored
  23. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  24. 2026-10-11 13:41 UTCEchelonGraph re-scored
  25. 2026-10-11 02:42 UTCEchelonGraph re-scored
  26. 2026-10-11 02:42 UTCGHSA enrichmentGHSA-2p8h-ph4h-rm2f · GitHub severity HIGH · GitHub CVSS 5.9
  27. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  28. 2026-10-10 03:55 UTCEchelonGraph re-scored
  29. 2026-10-10 03:55 UTCGHSA enrichmentGHSA-2p8h-ph4h-rm2f · GitHub severity HIGH · GitHub CVSS 5.9
  30. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  31. 2026-10-09 05:09 UTCEchelonGraph re-scored
  32. 2026-10-09 05:09 UTCGHSA enrichmentGHSA-2p8h-ph4h-rm2f · GitHub severity HIGH · GitHub CVSS 5.9
  33. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  34. 2026-10-08 06:23 UTCEchelonGraph re-scored
  35. 2026-10-08 06:23 UTCGHSA enrichmentGHSA-2p8h-ph4h-rm2f · GitHub severity HIGH · GitHub CVSS 5.9
  36. 2026-10-08 05:38 UTCEchelonGraph re-scored
  37. 2026-10-08 05:38 UTCGHSA enrichmentGHSA-2p8h-ph4h-rm2f · GitHub severity HIGH · GitHub CVSS 5.9
  38. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  39. 2026-10-07 13:47 UTCGHSA enrichmentGHSA-2p8h-ph4h-rm2f · GitHub severity HIGH · GitHub CVSS 5.9
  40. 2026-10-07 07:29 UTCEchelonGraph re-scored
  41. 2026-10-07 07:29 UTCGHSA enrichmentGHSA-2p8h-ph4h-rm2f · GitHub severity HIGH · GitHub CVSS 5.9
  42. 2026-10-07 06:24 UTCEchelonGraph re-scored
  43. 2026-10-07 06:23 UTCGHSA enrichmentGHSA-2p8h-ph4h-rm2f · GitHub severity HIGH · GitHub CVSS 5.9
  44. 2026-10-06 20:32 UTCEchelonGraph re-scored
  45. 2026-10-06 20:02 UTCEchelonGraph re-scored
  46. 2026-10-06 19:52 UTCEchelonGraph re-scoredFirst assessed: 5.9 MEDIUM
  47. 2026-10-06 19:51 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-94114?
CVE-2026-94114 is a medium-severity vulnerability; its CVE record was published on October 6, 2026. Symbolic name not mapping to correct class. BCEL caches attacker-controlled classes under their self-declared names without validating the requested name, allowing subsequent lookups and name-keyed verification results to refer to a different class. This issue affects Apache Commons BCEL: before…
When was the CVE record for CVE-2026-94114 published?
The CVE record for CVE-2026-94114 was published on October 6, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-94114 actively exploited?
CVE-2026-94114 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-94114?
CVE-2026-94114 has a CVSS base score of 5.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-94114?
A fix for CVE-2026-94114 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-94114 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-94114

Explore →

Is Your Infrastructure Affected by CVE-2026-94114?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.