cve.bz

CVE-2026-53910 gnu diffutils: Year 2038 problem, Y2K38, Y2038, Epochalypse

2.1 lowEPSS 0.3%

Low (2.1) in gnu diffutils. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
diff3 tool from GNU diffutils is vulnerable to a heap‑based buffer overflow due to multiple signed integer overflows in line‑mapping calculations. Incorrect arithmetic in mapping line ranges can result in corrupted values being used for memory allocation and loop bounds. When processing crafted diff output, these overflows may cause the application to allocate insufficient memory and subsequently perform out‑of‑bounds writes during internal processing.  An attacker who can control the output of the diff program used by diff3 (e.g. via --diff-program pointing to a malicious script) can trigger out-of-bounds writes, resulting in a crash and potentially remote code execution depending on the environment. This issue has been fixed in commit 9ff04d5b84743e331e80b589335a52c5480d1815  NOTE: The project maintainers claim that this is not a security issue. They state that the worst outcome this issue can cause is a crash of diff and that it cannot be used to escalate privileges.

Severity

CVSS 4.0

2.1 low
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:L/SI:L/SA:L
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 22nd percentile. Scored 2026-11-15. 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-07-22. 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-190 Integer Overflow or Wraparound (Year 2038 problem, Y2K38, Y2038, Epochalypse)
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-53910 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-53910?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-53910?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-53910 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-53910

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-53910](https://cve.bz/cve/badge/CVE-2026-53910.svg)](https://cve.bz/cve/CVE-2026-53910)

HTML:

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

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
GNU diffutilsthrough 3.12

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14diffutilsno fix listedDEBIAN-CVE-2026-53910
Ubuntu22.04:LTSdiffutils1:3.8-0ubuntu2.1UBUNTU-CVE-2026-53910 USN-8692-1
Ubuntu24.04:LTSdiffutils1:3.10-1ubuntu0.1UBUNTU-CVE-2026-53910 USN-8692-1
Ubuntu26.04:LTSdiffutils1:3.12-1ubuntu0.1UBUNTU-CVE-2026-53910 USN-8692-1
UbuntuPro:14.04:LTSdiffutils1:3.3-1ubuntu0.1~esm1UBUNTU-CVE-2026-53910 USN-8692-1
UbuntuPro:16.04:LTSdiffutils1:3.3-3ubuntu0.1~esm1UBUNTU-CVE-2026-53910 USN-8692-1
UbuntuPro:18.04:LTSdiffutils1:3.6-1ubuntu0.1~esm1UBUNTU-CVE-2026-53910 USN-8692-1
UbuntuPro:20.04:LTSdiffutils1:3.7-3ubuntu0.1~esm1UBUNTU-CVE-2026-53910 USN-8692-1
Red Hathummingbird:1diffutils0:3.12-6.1.hum1RHSA-2026:45327
Alpaquita25, streamdiffutils3.12-r1BELL-CVE-2026-53910
BellSoft Hardened Containers25, streamdiffutils3.12-r1BELL-CVE-2026-53910

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · Alpaquita · BellSoft Hardened Containers.

Red Hat

Red Hat rates this Low.

Red Hat's statement

To exploit this vulnerability, an attacker needs to be able to control the output of the diff program used by diff3 (e.g., via --diff-program pointing to a malicious script) or convince a user to execute diff3 with specially crafted diff output. An attacker often needs prior execution privileges to supply the malicious diff output, meaning they already have the ability to execute arbitrary scripts on the system. Due to these reasons, this vulnerability has been rated with a low severity.

Red Hat's mitigation

To mitigate this vulnerability, do not run the diff3 program with untrusted input for the --diff-program argument or process untrusted diff output.

ProductPackageStateAdvisory
Red Hat Hardened Imagesdiffutils-main-3.12-6.1.hum1Fixed 2026-07-24RHSA-2026:45327
Red Hat Enterprise Linux 10diffutilsFix deferred
Red Hat Enterprise Linux 6diffutilsFix deferred
Red Hat Enterprise Linux 7diffutilsFix deferred
Red Hat Enterprise Linux 8diffutilsFix deferred
Red Hat Enterprise Linux 9diffutilsFix deferred
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Fix deferred
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Fix deferred
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-53910.

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

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

References

Check your stackJSON