Symbolic Name not Mapping to Correct Object Affecting org.objenesis:objenesis package, versions [,3.6)


Severity

Recommended
0.0
low
0
10

CVSS assessment by Snyk's Security Team. Learn more

Threat Intelligence

EPSS
0.14% (3rd 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-JAVA-ORGOBJENESIS-21755439
  • published27 Oct 2026
  • disclosed26 Oct 2026
  • creditUnknown

Introduced: 26 Oct 2026

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

How to fix?

Upgrade org.objenesis:objenesis to version 3.6 or higher.

Overview

Affected versions of this package are vulnerable to Symbolic Name not Mapping to Correct Object through the getInstantiatorOf process. An attacker can cause objects from one class loader to be substituted into another by exploiting instantiator caching keyed on class name, potentially leading to unexpected behavior, data corruption, or application crashes by introducing wrong-class objects.

CVSS Base Scores

version 4.0
version 3.1