Skip to main content
VulnerabilityPublished

CVE-2026-124077: GitIdentifiers Class

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-124077· Medium

Not known to be exploited : upgrade to 1.23.0 when convenient.

Data as of 9 Nov 2026, 22:20 UTC

Severity
Medium

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 1.23.0, 87f6aa2818836998528ff4b0d1ea35545a800ee5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

What to do

Upgrade Apache Commons Codec and commons-codec/commons-codec to 1.23.0; Apache Commons Codec to 87f6aa2818836998528ff4b0d1ea35545a800ee5.

Affected software

ProductAffectedFixed in
Apache Commons Codeccommons-codec:commons-codecAffected
  • >=1.22.0 <1.23.0
Fixed in
  • 1.23.0
Apache Software FoundationApache Commons CodecAffected
  • ≥ 387120c901f4a75c3112dfdf8877dcdec7ae685d, < 87f6aa2818836998528ff4b0d1ea35545a800ee5
Fixed in
  • 87f6aa2818836998528ff4b0d1ea35545a800ee5
Mavencommons-codec/commons-codecpkg:maven/commons-codec/commons-codecOther threatsAffected
  • >=1.22.0 <1.23.0
Fixed in
  • 1.23.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

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.

References

Community reviews

Loading reviews…