cve.bz

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

4.3 mediumEPSS 0.3%

Medium (4.3) in apache software foundation apache commons codec. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

4.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
EPSS
0.3% estimated probability of exploitation activity in the next 30 days; 28th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-12. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-158 Improper Neutralization of Null Byte or NUL Character
Published
Modified
Assigned by
apache (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-124077 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-124077?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-124077?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-124077 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-124077

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-124077](https://cve.bz/cve/badge/CVE-2026-124077.svg)](https://cve.bz/cve/CVE-2026-124077)

HTML:

<a href="https://cve.bz/cve/CVE-2026-124077"><img src="https://cve.bz/cve/badge/CVE-2026-124077.svg" alt="CVE-2026-124077"></a>

Affected

  • apache software foundation:apache commons codec

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Commons Codecfrom 1.22.0 before 1.23.0

Fix and patched versions

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu14.04:LTS, 16.04:LTS, 18.04:LTS and 5 morelibcommons-codec-javano fix listedUBUNTU-CVE-2026-124077
openSUSETumbleweedapache-commons-codec1.23.0-1.1openSUSE-SU-2026:12523-1

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu · openSUSE.

Attack patterns (CAPEC)

  • CAPEC-52 Embedding NULL Bytes Likelihood: High · Severity: High
  • CAPEC-53 Postfix, Null Terminate, and Backslash Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

  1. Scored 4.3 medium

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON