# CVE-2026-94114: Apache Commons BCEL: Class repositories cache class files under their self-declared names, enabling cache poisoning

> Attackers can poison the class cache in Apache Commons BCEL by exploiting name mismatches, potentially leading to code execution or bypassing verification.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Oct 2026
- **Updated:** 8 Oct 2026
- **Also known as:** AZL-108017, DEBIAN-CVE-2026-94114, GHSA-2p8h-ph4h-rm2f, UBUNTU-CVE-2026-94114

## What is CVE-2026-94114?

CVE-2026-94114 is a high-severity vulnerability in Apache Commons BCEL, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Symbolic name not mapping to correct class.

BCEL caches attacker-controlled classes under their self-declared names without validating the requested name, allowing subsequent lookups and name-keyed verification results to refer to a different class.

This issue affects Apache Commons BCEL: before 6.13.0.

Users are recommended to upgrade to version 6.13.0, which fixes the issue.

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-94114 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-94114 is a high-severity vulnerability in Apache Commons BCEL, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-94114 in the wild and no public exploit code.

Affected product: Apache Commons BCEL. 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-94114/ (Markdown: https://insights.sbomify.com/CVE-2026-94114/index.md)
```

## Sources

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

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