{"api_version":"1","generated_at":"2026-11-10T07:45:41+00:00","cve":"CVE-2026-124077","urls":{"html":"https://cve.report/CVE-2026-124077","api":"https://cve.report/api/cve/CVE-2026-124077.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-124077","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-124077"},"summary":{"title":"Apache Commons Codec: NUL bytes in tree entry names cause Git/SWHID identifier collisions (GitIdentifiers class)","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.\n\n\n\nThe 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.\n\n\n\nThis issue affects Apache Commons Codec: from 1.22.0 before 1.23.0.\n\n\n\nUsers are recommended to upgrade to version 1.23.0, which fixes the issue.","state":"PUBLISHED","assigner":"apache","published_at":"2026-11-09 20:18:10","updated_at":"2026-11-10 01:17:17"},"problem_types":["CWE-158","CWE-158 CWE-158 Improper neutralization of null byte or NUL character"],"metrics":[],"references":[{"url":"https://github.com/apache/commons-codec/commit/87f6aa2818836998528ff4b0d1ea35545a800ee5.patch","name":"https://github.com/apache/commons-codec/commit/87f6aa2818836998528ff4b0d1ea35545a800ee5.patch","refsource":"security@apache.org","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://lists.apache.org/thread.html/zns7tbnkq685prps9d85q7ct6oobvzsm","name":"https://lists.apache.org/thread.html/zns7tbnkq685prps9d85q7ct6oobvzsm","refsource":"security@apache.org","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"http://www.openwall.com/lists/oss-security/2026/11/09/30","name":"http://www.openwall.com/lists/oss-security/2026/11/09/30","refsource":"af854a3a-2127-422b-91ae-364da2661108","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-124077","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-124077","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Apache Software Foundation","product":"Apache Commons Codec","version":"affected 1.22.0 1.23.0 maven","platforms":[]},{"source":"CNA","vendor":"Apache Software Foundation","product":"Apache Commons Codec","version":"affected 387120c901f4a75c3112dfdf8877dcdec7ae685d 87f6aa2818836998528ff4b0d1ea35545a800ee5 git","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[{"source":"CNA","value":"Claude Security","lang":"en"},{"source":"CNA","value":"Gary D. Gregory","lang":"en"}],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"adp":[{"providerMetadata":{"dateUpdated":"2026-11-10T00:11:06.971Z","orgId":"af854a3a-2127-422b-91ae-364da2661108","shortName":"CVE"},"references":[{"url":"http://www.openwall.com/lists/oss-security/2026/11/09/30"}],"title":"CVE Program Container"}],"cna":{"affected":[{"collectionURL":"https://repo.maven.apache.org/maven2","defaultStatus":"unaffected","packageName":"commons-codec:commons-codec","packageURL":"pkg:maven/commons-codec/commons-codec","product":"Apache Commons Codec","vendor":"Apache Software Foundation","versions":[{"lessThan":"1.23.0","status":"affected","version":"1.22.0","versionType":"maven"}]},{"defaultStatus":"unaffected","product":"Apache Commons Codec","repo":"https://gitbox.apache.org/repos/asf/commons-codec.git","vendor":"Apache Software Foundation","versions":[{"lessThan":"87f6aa2818836998528ff4b0d1ea35545a800ee5","status":"affected","version":"387120c901f4a75c3112dfdf8877dcdec7ae685d","versionType":"git"}]}],"credits":[{"lang":"en","type":"tool","value":"Claude Security"},{"lang":"en","type":"remediation developer","value":"Gary D. Gregory"}],"descriptions":[{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"<p>The <code>GitIdentifiers</code> 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.</p><p>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.</p><p>This issue affects Apache Commons Codec: from 1.22.0 before 1.23.0.</p><p>Users are recommended to upgrade to version 1.23.0, which fixes the issue.</p>"}],"value":"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.\n\n\n\nThe 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.\n\n\n\nThis issue affects Apache Commons Codec: from 1.22.0 before 1.23.0.\n\n\n\nUsers are recommended to upgrade to version 1.23.0, which fixes the issue."}],"metrics":[{"other":{"content":{"text":"low"},"type":"Textual description of severity"},"scenarios":[{"lang":"en","value":"GENERAL"}]}],"problemTypes":[{"descriptions":[{"cweId":"CWE-158","description":"CWE-158 Improper neutralization of null byte or NUL character","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-11-09T20:10:42.190Z","orgId":"f0158376-9dc2-43b6-827c-5f631a4d8d09","shortName":"apache"},"references":[{"tags":["patch"],"url":"https://github.com/apache/commons-codec/commit/87f6aa2818836998528ff4b0d1ea35545a800ee5.patch"},{"tags":["vendor-advisory"],"url":"https://lists.apache.org/thread.html/zns7tbnkq685prps9d85q7ct6oobvzsm"}],"source":{"discovery":"INTERNAL"},"title":"Apache Commons Codec: NUL bytes in tree entry names cause Git/SWHID identifier collisions (GitIdentifiers class)","x_generator":{"engine":"Vulnogram 1.0.3"}}},"cveMetadata":{"assignerOrgId":"f0158376-9dc2-43b6-827c-5f631a4d8d09","assignerShortName":"apache","cveId":"CVE-2026-124077","datePublished":"2026-11-09T20:10:42.190Z","dateReserved":"2026-11-06T20:45:11.690Z","dateUpdated":"2026-11-10T00:11:06.971Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-09 20:18:10","lastModifiedDate":"2026-11-10 01:17:17","problem_types":["CWE-158","CWE-158 CWE-158 Improper neutralization of null byte or NUL character"],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"124077","Ordinal":"1","Title":"Apache Commons Codec: NUL bytes in tree entry names cause Git/SW","CVE":"CVE-2026-124077","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"124077","Ordinal":"1","NoteData":"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.\n\n\n\nThe 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.\n\n\n\nThis issue affects Apache Commons Codec: from 1.22.0 before 1.23.0.\n\n\n\nUsers are recommended to upgrade to version 1.23.0, which fixes the issue.","Type":"Description","Title":"Apache Commons Codec: NUL bytes in tree entry names cause Git/SW"}]}}}