CVE-2026-119078 · Package
NO FIX YET · SEE WHAT TO DO
The Blake3 class in Apache Commons Codec documented that repeated doFinalize calls return different output, but they return the same bytes. An application that derives several keys with consecutive doFinalize calls ends up with identical keys, so the separation between them is lost.
first public Nov 9, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Applications that use Apache Commons Codec's Blake3 class from 1.16.0 up to 1.23.0 and call doFinalize more than once on the same instance to get new output, such as key derivation following the old Javadoc example. Code that uses Blake3 once per instance, or does not use Blake3 at all, is not affected.
Not affected if no-blake3-usage, single-dofinalize-per-instance
Who cares apache-commons-codec, blake3, java, key-derivation
Blake3 and for more than one doFinalize call on the same instance.1.16.0 up to but not including 1.23.0.1.23.0 or later, which corrects the documentation only.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.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.