# CVE-2026-116486: Objenesis before 3.6 Type Confusion via Class Name Instantiator Cache


- **Severity:** Low 2.0 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** AZL-111112, DEBIAN-CVE-2026-116486, GHSA-743r-26gf-97ff, GHSA-h635-rrqm-4mjq, UBUNTU-CVE-2026-116486

## What is CVE-2026-116486?

CVE-2026-116486 is a low-severity vulnerability in easymock objenesis, published on 26 Oct 2026. 

### Official 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.

Weakness: CWE-386 (Symbolic Name not Mapping to Correct Object)

## Which versions are affected by CVE-2026-116486?


## How do I fix CVE-2026-116486?

Upgrade to a fixed version.

## Is CVE-2026-116486 being exploited?

There is no known exploitation of CVE-2026-116486 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-116486 and fix it if it is affected.

What it is: CVE-2026-116486 is a low-severity vulnerability in easymock objenesis, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116486 in the wild and no public exploit code.

Affected product: easymock objenesis. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-116486/ (Markdown: https://insights.sbomify.com/CVE-2026-116486/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-116486
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-116486
- OSV: https://osv.dev/vulnerability/CVE-2026-116486

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-116486/
Summaries are generated and may contain mistakes; the official description above is the record.