Blake3 doFinalize returns identical output in Apache Commons Codec
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- High · High · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA.
Summary
Apache Commons Codec from 1.16.0 before 1.23.0 has a flaw in the doFinalize methods of its Blake3 class. The Javadoc wrongly says that doFinalize output depends on previously finalized bytes, but doFinalize does not change the hash state, so a repeated call without new input returns the same bytes. The key-derivation example in the Javadoc calls doFinalize twice, so the two derived keys come out identical and lose their separation.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
Upgrade to Apache Commons Codec 1.23.0, which corrects the documentation but does not change doFinalize, so affected code must also change. Check 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.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
- Fix · CNA Apache Commons Codec (Apache Software Foundation) Fixed in 1.23.0
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
Apache Commons Codec 1.23.0
2 records Highest priority Priority MEDIUM 1 MEDIUM, 1 LOW
Other records, highest priority first
- TI-2026-87344 NUL bytes in tree entry names cause Git identifier collisionsPriority LOW 20
Timeline
- 2026-11-09 Threatist record created from CVE-2026-119078
- 2026-11-09 Alias added: GHSA-rv28-228v-c565
- 2026-11-12 CVSS score added · CISA ADP
- 2026-11-12 CISA SSVC decision points changed
References
More Apache vulnerabilities
- TI-2025-18529 Path equivalence in Apache Tomcat allows code execution via PUT KEVCVSS 3.1CRITICAL 10.0
- TI-2024-30292 Forced browsing in Apache OFBiz bypasses controller-view authorization KEVCVSS 3.1CRITICAL 9.8
- TI-2024-26062 Incorrect authorization in Apache OFBiz exposes screen rendering code KEVCVSS 3.1CRITICAL 9.8
- TI-2024-21190 Path traversal in Apache OFBiz leads to remote code execution KEVCVSS 3.1CRITICAL 9.8
- TI-2024-18186 Remote command execution in Apache HugeGraph-Server via Gremlin KEVCVSS 3.1CRITICAL 9.8
- TI-2023-25106 Apache ActiveMQ OpenWire deserialization allows remote code execution KEVCVSS 3.1CRITICAL 10.0
Sources
- CVE-2026-119078 · CVE Program
- CVE-2026-119078 · NVD
- FIRST EPSS
- GHSA-rv28-228v-c565 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences