Symbolic Name not Mapping to Correct Object Affecting objenesis package, versions *


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. 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-DEBIAN12-OBJENESIS-21755516
  • published27 Oct 2026
  • disclosed26 Oct 2026

Introduced: 26 Oct 2026

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

How to fix?

There is no fixed version for Debian:12 objenesis.

NVD Description

Note: Versions mentioned in the description apply only to the upstream objenesis package and not the objenesis package as distributed by Debian. See How to fix? for Debian:12 relevant fixed versions and status.

Objenesis before 3.6 contains a type confusion vulnerability that allows code in one class loader to substitute objects into another by exploiting instantiator caching keyed on class name. When a shared ObjenesisStd instance caches instantiators by clazz.getName() in ObjenesisBase.getInstantiatorOf(), same-named classes collide, causing newInstance() to return wrong-class objects and ClassCastException failures.

CVSS Base Scores

version 3.1