CVE-2026-56289

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 5.5 from GitHub Security Advisory published 2026-07-09. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

GNU patch is vulnerable to a denial of service (DoS) due to improper validation of hunk (single block of changes in diff) line offsets in unified-diff input. A specially crafted patch can specify an extremely large line number, causing the application to enter an effectively infinite processing loop while attempting to locate the requested position. This results in excessive CPU consumption and prevents the process from completing. An attacker can trigger this behavior by supplying a malicious patch file, causing the utility to become unresponsive and require manual termination.

This issue has been fixed in the commit faba04ef4f2b410257f76c1b9dc85e350929c4b9

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
The EG Score, 5.5 of 10.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 9, 2026

Last Modified

July 13, 2026

Advisory Details (1)

Auto-updated Jul 9, 2026
Patch available.
Web page

Vulnerabilities in GNU patch software | CERT Polska

https://cert.pl/en/posts/2026/07/CVE-2026-56288

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatpatch-main-2.8-4.2.hum12026-07-10redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
patch2.7.6-7, 2.8-1, 2.8-2
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
patch2.7.6-7, 2.8-1, 2.8-2
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
patch2.8-2
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
patch2.8-2
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 52× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 220 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 120 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 19:38 UTCEG score recompute
  2. 2026-10-11 16:53 UTCEG score recompute
  3. 2026-10-11 14:16 UTCEG score recompute
  4. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  5. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  6. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  7. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  8. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  9. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  10. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  11. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  12. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  13. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  14. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  15. 2026-10-01 16:05 UTCEG score recompute
  16. 2026-10-01 16:05 UTCVendor advisory
  17. 2026-10-01 16:05 UTCGHSA enrichmentGHSA-3m3r-f94v-4mf8 · GitHub CVSS 5.5
  18. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  19. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  20. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  21. 2026-09-28 10:59 UTCEG score recompute
  22. 2026-09-28 10:59 UTCVendor advisory
  23. 2026-09-28 10:59 UTCGHSA enrichmentGHSA-3m3r-f94v-4mf8 · GitHub CVSS 5.5
  24. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  25. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 5th percentile
Show 75 more
  1. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-09-24 11:41 UTCEG score recompute
  3. 2026-09-24 11:41 UTCVendor advisory
  4. 2026-09-24 11:41 UTCGHSA enrichmentGHSA-3m3r-f94v-4mf8 · GitHub CVSS 5.5
  5. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  6. 2026-09-23 06:00 UTCEG score recompute
  7. 2026-09-23 06:00 UTCVendor advisory
  8. 2026-09-23 06:00 UTCGHSA enrichmentGHSA-3m3r-f94v-4mf8 · GitHub CVSS 5.5
  9. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  10. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-09-18 05:38 UTCEG score recompute
  12. 2026-09-18 05:38 UTCVendor advisory
  13. 2026-09-18 05:38 UTCGHSA enrichmentGHSA-3m3r-f94v-4mf8 · GitHub CVSS 5.5
  14. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  15. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  17. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  18. 2026-09-14 07:38 UTCEG score recompute
  19. 2026-09-14 07:38 UTCVendor advisory
  20. 2026-09-14 07:38 UTCGHSA enrichmentGHSA-3m3r-f94v-4mf8 · GitHub CVSS 5.5
  21. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  22. 2026-09-13 08:20 UTCEG score recompute
  23. 2026-09-13 08:20 UTCVendor advisory
  24. 2026-09-13 08:20 UTCGHSA enrichmentGHSA-3m3r-f94v-4mf8 · GitHub CVSS 5.5
  25. 2026-09-12 03:25 UTCEG score recompute
  26. 2026-09-12 03:25 UTCVendor advisory
  27. 2026-09-12 03:25 UTCGHSA enrichmentGHSA-3m3r-f94v-4mf8 · GitHub CVSS 5.5
  28. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  29. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  30. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  31. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  32. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  33. 2026-09-05 22:36 UTCEG score recompute
  34. 2026-09-05 22:36 UTCVendor advisory
  35. 2026-09-05 22:36 UTCGHSA enrichmentGHSA-3m3r-f94v-4mf8 · GitHub CVSS 5.5
  36. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  37. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  38. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  39. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  40. 2026-08-30 06:57 UTCEG score recompute
  41. 2026-08-30 06:57 UTCVendor advisory
  42. 2026-08-30 06:57 UTCGHSA enrichmentGHSA-3m3r-f94v-4mf8 · GitHub CVSS 5.5
  43. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  44. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  45. 2026-08-28 02:42 UTCEG score recompute
  46. 2026-08-28 02:42 UTCVendor advisory
  47. 2026-08-28 02:42 UTCGHSA enrichmentGHSA-3m3r-f94v-4mf8 · GitHub CVSS 5.5
  48. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  49. 2026-08-27 03:14 UTCEG score recompute
  50. 2026-08-27 03:14 UTCVendor advisory
  51. 2026-08-27 03:14 UTCGHSA enrichmentGHSA-3m3r-f94v-4mf8 · GitHub CVSS 5.5
  52. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  53. 2026-08-26 03:55 UTCEG score recompute
  54. 2026-08-26 03:55 UTCVendor advisory
  55. 2026-08-26 03:55 UTCGHSA enrichmentGHSA-3m3r-f94v-4mf8 · GitHub CVSS 5.5
  56. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  57. 2026-08-24 22:24 UTCEG score recompute
  58. 2026-08-24 22:24 UTCVendor advisory
  59. 2026-08-24 22:24 UTCGHSA enrichmentGHSA-3m3r-f94v-4mf8 · GitHub CVSS 5.5
  60. 2026-08-23 23:05 UTCEG score recompute
  61. 2026-08-23 23:05 UTCVendor advisory
  62. 2026-08-23 23:05 UTCGHSA enrichmentGHSA-3m3r-f94v-4mf8 · GitHub CVSS 5.5
  63. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  64. 2026-08-22 23:47 UTCVendor advisory
  65. 2026-08-22 23:47 UTCGHSA enrichmentGHSA-3m3r-f94v-4mf8 · GitHub CVSS 5.5
  66. 2026-08-22 00:28 UTCEG score recompute
  67. 2026-08-22 00:28 UTCVendor advisory
  68. 2026-08-22 00:28 UTCGHSA enrichmentGHSA-3m3r-f94v-4mf8 · GitHub CVSS 5.5
  69. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  70. 2026-08-21 01:09 UTCEG score recompute
  71. 2026-08-21 01:09 UTCVendor advisory
  72. 2026-08-21 01:09 UTCGHSA enrichmentGHSA-3m3r-f94v-4mf8 · GitHub CVSS 5.5
  73. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  74. 2026-08-20 01:51 UTCEG score recompute
  75. 2026-08-20 01:51 UTCGHSA enrichmentGHSA-3m3r-f94v-4mf8 · GitHub CVSS 5.5

Frequently asked(5)

What is CVE-2026-56289?
CVE-2026-56289 is a medium-severity vulnerability; its CVE record was published on July 9, 2026. GNU patch is vulnerable to a denial of service (DoS) due to improper validation of hunk (single block of changes in diff) line offsets in unified-diff input. A specially crafted patch can specify an extremely large line number, causing the application to enter an effectively infinite processing…
When was the CVE record for CVE-2026-56289 published?
The CVE record for CVE-2026-56289 was published on July 9, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 13, 2026; the record at its source may have been updated since.
Is CVE-2026-56289 actively exploited?
CVE-2026-56289 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56289?
CVE-2026-56289 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-56289?
A fix for CVE-2026-56289 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-56289 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-56289

Explore →

Is Your Infrastructure Affected by CVE-2026-56289?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.