Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Mon, 26 Oct 2026 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Easymock
Easymock objenesis |
|
| Vendors & Products |
Easymock
Easymock objenesis |
Mon, 26 Oct 2026 17:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Mon, 26 Oct 2026 14:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Objenesis before 3.6 Type Confusion via Class Name Instantiator Cache | |
| Weaknesses | CWE-386 | |
| References |
|
|
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2026-10-26T16:15:59.231Z
Reserved: 2026-10-26T11:37:37.948Z
Link: CVE-2026-116486
Updated: 2026-10-26T15:38:11.478Z
Status : Awaiting Analysis
Published: 2026-10-26T14:16:37.200
Modified: 2026-10-26T18:39:42.503
Link: CVE-2026-116486
No data.
OpenCVE Enrichment
Updated: 2026-10-26T18:50:39Z