CVE-2026-116486

Published: Ott 26, 2026 Last Modified: Ott 26, 2026
ExploitDB:
Other exploit source:
Google Dorks:
LOW 2,0
Attack Vector: local
Attack Complexity: high
Privileges Required: low
User Interaction: none
Confidentiality: N/A
Integrity: N/A
Availability: N/A
MEDIUM 4,5
Attack Vector: local
Attack Complexity: high
Privileges Required: low
User Interaction: none
Scope: unchanged
Confidentiality: low
Integrity: low
Availability: low

Description

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.

386

Symbolic Name not Mapping to Correct Object

Draft
Common Consequences
Security Scopes Affected:
Access Control Integrity Confidentiality Other Non-Repudiation
Potential Impacts:
Gain Privileges Or Assume Identity Modify Application Data Modify Files Or Directories Read Application Data Read Files Or Directories Other Hide Activities
Applicable Platforms
All platforms may be affected
View CWE Details
https://github.com/easymock/objenesis
https://github.com/easymock/objenesis/blob/fb36e5c377ed1bf57a18386fa79d2eed4ddf…
https://github.com/easymock/objenesis/commit/40f90f435a06b16af74a7398f0007faeaa…
https://github.com/easymock/objenesis/security/advisories/GHSA-743r-26gf-97ff
https://www.vulncheck.com/advisories/objenesis-before-3.6-type-confusion-via-cl…