CVE-2026-94114
Published:October 06, 2026
Updated:October 10, 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 6.13.0.
Users are recommended to upgrade to version 6.13.0, which fixes the issue.
Affected Packages
https://github.com/apache/commons-bcel.git (GITHUB):
Affected version(s) >=rel/commons-bcel-6.4.0 <rel/commons-bcel-6.13.0Fix Suggestion:
Update to version rel/commons-bcel-6.13.0org.apache.bcel:bcel (JAVA):
Affected version(s) >=6.0 <6.13.0Fix Suggestion:
Update to version 6.13.0Related Resources (8)
Do you need more information?
Contact UsCVSS v4
Base Score:
8.2
Attack Vector
NETWORK
Attack Complexity
LOW
Attack Requirements
PRESENT
Privileges Required
NONE
User Interaction
NONE
Vulnerable System Confidentiality
NONE
Vulnerable System Integrity
HIGH
Vulnerable System Availability
NONE
Subsequent System Confidentiality
NONE
Subsequent System Integrity
NONE
Subsequent System Availability
NONE
CVSS v3
Base Score:
5.9
Attack Vector
NETWORK
Attack Complexity
HIGH
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
HIGH
Availability
NONE
Weakness Type (CWE)
Symbolic Name not Mapping to Correct Object
EPSS
Base Score:
0.28