Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-53910Published 2026-07-22

CVE-2026-53910 — GNU diffutils

low (derived)

As of 2026-07-27, CVE-2026-53910 is a Low-severity (band derived from the CVSS v4.0 score, not stated by the CNA) vulnerability in GNU diffutils, CVSS v4.0 2.1, EPSS 0.3% (24.3th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-53910, most recently “CVE-2026-53910: Heap-Based Buffer Overflow in GNU diffutils diff3 (Signed Integer Overflow)”.

CVSS v4.0
2.1/10Low (derived)
EPSS
0.3%Higher than 24.3% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
1Campaigns referencing it
Priority
2/10Threadlinqs triage score
Published
Updated 2026-07-27
CVSS v4.0 2.1 (Low, derived from score) · EPSS 0.3% (higher than 24.3% of all scored CVEs) · Priority 2/10 · Published 2026-07-22

Last updated:

What is CVE-2026-53910?

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.

The record classifies CVE-2026-53910 under weakness class CWE-190. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 117 days ago.

Severity and exploitation probability

CVSS v4.0 base score
2.1 — Low (derived from score)
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 (FIRST)
0.3% probability of exploitation in the next 30 days, higher than 24.3% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
2/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-07-22

Is CVE-2026-53910 being exploited?

It currently carries a trending score of 21 in the Threadlinqs vulnerability feed.

Affected products and versions

How to fix CVE-2026-53910

Patch reference: https://cgit.git.savannah.gnu.org/cgit/diffutils.git/commit/?id=73ed7ce85cc78effb94daf028c9af6b4e5252e50. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

Threat activity tracking CVE-2026-53910

1 tracked threat in the Threadlinqs corpus references CVE-2026-53910, either in the campaign’s CVE list or as an indicator on the campaign record.

Sources

Enriched from CVE.org, FIRST EPSS, GitHub Security Advisories.

Vendor advisory and patch

Third-party advisory

Issue tracking and product pages