NUL bytes in tree entry names cause Git identifier collisions
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- Required
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- Low · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA.
Summary
Apache Commons Codec from 1.22.0 before 1.23.0 does not reject NUL bytes in tree entry names in its GitIdentifiers class. Because Git uses a NUL byte to end each entry name, a crafted name can make two different directory trees produce the same Git tree identifier or SWHID, which is a CWE-158 flaw. A remote attacker without privileges can exploit it only in applications that build trees from names supplied by other sources, such as ZIP archive entries or names passed directly to the API, since common file systems do not allow NUL bytes in file names.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the CNA
The GitIdentifiers class in Apache Commons Codec did not reject NUL bytes in tree entry names. Because Git uses a NUL byte to mark the end of each entry name in a tree object, a crafted name could make one tree serialize to the same bytes as a different tree. Two different directory trees could then receive the same Git tree identifier or SWHID. The impact is limited: common file systems do not allow NUL bytes in file names, so trees built by walking a file system are not affected. Only applications that build trees from names supplied by other sources, such as entries of archive formats that permit NUL bytes in names (e.g. ZIP) or names passed directly to the API, are exposed. This issue affects Apache Commons Codec: from 1.22.0 before 1.23.0. Users are recommended to upgrade to version 1.23.0, which fixes the issue.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
Upgrade Apache Commons Codec to version 1.23.0, which fixes the issue.
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-87343 Blake3 doFinalize returns identical output in Apache Commons CodecPriority MEDIUM 47
Timeline
- 2026-11-09 Threatist record created from CVE-2026-124077
- 2026-11-09 Alias added: GHSA-26mf-gqw6-894w
- 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-124077 · CVE Program
- CVE-2026-124077 · NVD
- FIRST EPSS
- GHSA-26mf-gqw6-894w · 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