Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
9.1
CVE-2026-119078: Apache Commons Codec Blake3 can produce duplicate keys
CVE-2026-119078 · published 10 days ago
Summary
The Blake3 component in Apache Commons Codec (versions 1.16.0 through 1.22.x) returns the same bytes each time its final step is called, so code that expects a new key on each call will actually get identical keys. This can weaken any system that relies on separate keys being generated from the same Blake3 instance. Review your applications for repeated calls to the final step on a single Blake3 object and instead request the total needed length in one call and split the result, or update the code according to the revised documentation.
What to do
- Update apache software foundation apache commons codec to version 1.23.0 or later.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| – | apache software foundation | apache commons codec | < 1.23.0 |
| Ubuntu:14.04:LTS | canonical | libcommons-codec-java | All versions |
Original advisory text
Apache Commons Codec: Blake3 doFinalize is stateless; the documented KDF example derives identical keys
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.
References
- https://lists.apache.org/thread.html/ol71kdgopfxwlxgqmkd0jrfcw05wdq5z Third Party Advisory
- http://www.openwall.com/lists/oss-security/2026/11/09/29 Third Party Advisory
- https://ubuntu.com/security/CVE-2026-119078 Third Party Advisory
- https://www.cve.org/CVERecord?id=CVE-2026-119078 Third Party Advisory
Internet-facing
3 days
Internal
60 days
- Not known to be exploited
- Can be exploited automatically
- Gives an attacker full control
Severity
9.1
Critical
Type
CWE-684Incorrect Provision of Specified Functionality
CWE-1068Inconsistency Between Implementation and Documented Design
Timeline
Published12 Nov 2026
Updated22 Nov 2026
First seen9 Nov 2026
Track software like this
Free during beta