CVE-2026-124077 PUBLISHED

Apache Commons Codec: NUL bytes in tree entry names cause Git/SWHID identifier collisions (GitIdentifiers class)

Assigner: apache
Reserved: 06.11.2026 Published: 09.11.2026 Updated: 10.11.2026

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.

Product Status

Vendor Apache Software Foundation
Product Apache Commons Codec
Versions Default: unaffected
  • affected from 1.22.0 to 1.23.0 (excl.)
Vendor Apache Software Foundation
Product Apache Commons Codec
Versions Default: unaffected
  • affected from 387120c901f4a75c3112dfdf8877dcdec7ae685d to 87f6aa2818836998528ff4b0d1ea35545a800ee5 (excl.)

Credits

  • Claude Security tool
  • Gary D. Gregory remediation developer

References

Problem Types

  • CWE-158 Improper neutralization of null byte or NUL character CWE