Apache Commons Codec: NUL bytes in tree entry names cause Git/SWHID identifier collisions (GitIdentifiers class)
Affected packages
| Package | Affected → Fixed | |
|---|---|---|
| Apache Software FoundationApache Commons Codec |
≥ 387120c901f4a75c3112dfdf8877dcdec7ae685d, < 87f6aa2818836998528ff4b0d1ea35545a800ee5→ 87f6aa2818836998528ff4b0d1ea35545a800ee5 |
87f6aa2818836998528ff4b0d1ea35545a800ee5 |
Fix status by distribution
Records published by each distribution for this CVE. Fixed versions differ by release; check each link.
- Ubuntu UBUNTU-CVE-2026-124077 libcommons-codec-java No fixed version in this record
Original description The description as published by the source.
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.
Source: CVE.org (CVE Program・cvelistV5) NVD GitHub Advisory
References
- advisory lists.apache.org
- advisory nvd.nist.gov
- advisory github.com
- package gitbox.apache.org
- patch github.com
- web github.com
- web openwall.com
- web repo.maven.apache.org