CVE & CISA-KEV Catalog

CVE-2026-124077

MEDIUM
4.3
CVSS v3
NVD

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.

How to fix

No published remediation has been found for this vulnerability's affected products yet.

Mitigation guidance may be in the linked vendor advisories in the References section below.

TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works

CVSS v3 Vector

Exploitability

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionRequired
ScopeUnchanged

Impact

ConfidentialityLow
IntegrityNone
AvailabilityNone

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N

Exploit Intelligence

0.34%probability of exploitation in 30 days
28thpercentile

Low risk: more likely to be exploited than 28% of all known CVEs.

References

Related Vulnerabilities

Other CWE-158 vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2025-47812Critical10.094%KEVFix
CVE-2009-1537High8.851%KEV-
CVE-2022-20812Critical9.02.0%-Fix
CVE-2020-14500Critical10.01.7%--
CVE-2020-7928Medium6.51.4%-Fix
CVE-2022-20813Critical9.01.1%-Fix

Common questions

How do I fix CVE-2026-124077?

No published fix for CVE-2026-124077 has been found yet. Check the linked vendor advisories for guidance as it becomes available.

Is CVE-2026-124077 being actively exploited?

Not that we know of. CVE-2026-124077 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.34% is the estimated probability that it will be exploited in the next 30 days. That is higher than 28% of all scored CVEs.

How severe is CVE-2026-124077?

CVE-2026-124077 has a CVSS v3 base score of 4.3, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.

Embed a live status badge for CVE-2026-124077
CVE-2026-124077 severity badge

Markdown

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

HTML

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

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

Run a free CVE scan on your fleetStart freeThis CVE lookup is free and always will be.

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-11-12.