Symbolic Name not Mapping to Correct Object Affecting maven-shared-jar-javadoc package, versions *


Severity

Recommended
0.0
medium
0
10

Based on CentOS security rating.

Threat Intelligence

EPSS
0.28% (19th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CENTOS7-MAVENSHAREDJARJAVADOC-21104266
  • published16 Oct 2026
  • disclosed6 Oct 2026

Introduced: 6 Oct 2026

NewCVE-2026-94114  (opens in a new tab)
CWE-386  (opens in a new tab)

How to fix?

There is no fixed version for Centos:7 maven-shared-jar-javadoc.

NVD Description

Note: Versions mentioned in the description apply only to the upstream maven-shared-jar-javadoc package and not the maven-shared-jar-javadoc package as distributed by Centos. See How to fix? for Centos:7 relevant fixed versions and status.

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 Base Scores

version 3.1