CVE-2026-119078
CRITICALDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 34% of all known CVEs.
References
Related Vulnerabilities
Other CWE-684 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2023-5363 | High | 7.5 | 3.9% | - | Fix |
| CVE-2025-47227 | High | 7.5 | 1.9% | - | - |
| CVE-2020-11054 | Low | 3.5 | 1.5% | - | Fix |
| CVE-2026-34478 | High | 7.5 | 1.0% | - | Fix |
| CVE-2023-24845 | Critical | 9.1 | 0.7% | - | - |
| CVE-2023-4258 | High | 8.6 | 0.6% | - | Fix |
Common questions
How do I fix CVE-2026-119078?
No published fix for CVE-2026-119078 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-119078 being actively exploited?
Not that we know of. CVE-2026-119078 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.40% is the estimated probability that it will be exploited in the next 30 days. That is higher than 34% of all scored CVEs.
How severe is CVE-2026-119078?
CVE-2026-119078 has a CVSS v3 base score of 9.1, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-119078
Markdown
[](https://tridentstack.com/cve/CVE-2026-119078)HTML
<a href="https://tridentstack.com/cve/CVE-2026-119078"><img src="https://tridentstack.com/cve/badge/CVE-2026-119078.svg" alt="CVE-2026-119078"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-11-12.