CVE-2026-78002

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.8% (56th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw was found in rsyslog. An unauthenticated remote attacker can trigger a heap buffer overflow in the RainerScript replace() function by sending specially crafted syslog messages. This vulnerability arises from an incorrect buffer size calculation during string replacement, causing memory corruption. Successful exploitation can lead to a denial of service (DoS) for the affected system.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.8% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.8%
EPSS %ILE
56th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.8% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

August 27, 2026

Last Modified

October 19, 2026

Advisory Details (3)

Auto-updated Aug 27, 2026
Patch available. Sources: redhat, github.
GitHub advisoryMentions a patch (unverified)

RainerScript `replace()` heap buffer overflow · Advisory · rsyslog/rsyslog · GitHub

https://github.com/rsyslog/rsyslog/security/advisories/GHSA-g72f-gc6v-f2w3
Red Hat

2521135 – (CVE-2026-78002) CVE-2026-78002 rsyslog: rsyslog: Denial of service via heap buffer overflow in RainerScript replace() function

https://bugzilla.redhat.com/show_bug.cgi?id=2521135
Red HatMentions a patch (unverified)

CVE-2026-78002 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-78002

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntursyslog-snmp (8.2112.0-2ubuntu2.5) @ jammy2026-10-19ubuntu
redhatrsyslog-0:8.2412.0-1.el10_0.22026-10-12redhat
redhatrsyslog-0:8.2102.0-15.el8_10.32026-10-12redhat
redhatrhui5/haproxy-rhel9:17902419002026-09-24redhat
redhatrsyslog-0:8.2510.0-2.el9_8.22026-09-22redhat
redhatrsyslog-0:8.2510.0-5.el10_2.22026-09-21redhat

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
rsyslog8.2302.0-1 ... 8.2608.0-4 (55 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rsyslog8.2504.0-1, 8.2504.0-1+deb13u1
  • every version up to 8.2504.0-1+deb13u2: fixed in 8.2504.0-1+deb13u2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
rsyslog8.2504.0-1 ... 8.2608.0-3 (26 versions)
  • every version up to 8.2608.0-4: fixed in 8.2608.0-4
—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 12× in last 7d / 118× 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 192 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 92 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-78002?
CVE-2026-78002 is a high-severity vulnerability; its CVE record was published on August 27, 2026. A flaw was found in rsyslog. An unauthenticated remote attacker can trigger a heap buffer overflow in the RainerScript replace() function by sending specially crafted syslog messages. This vulnerability arises from an incorrect buffer size calculation during string replacement, causing memory…
When was CVE-2026-78002 made public?
CVE-2026-78002 was made public on August 26, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on August 27, 2026. EchelonGraph's copy of the record carries a last-modified date of October 19, 2026; the record at its source may have been updated since.
Is CVE-2026-78002 actively exploited?
CVE-2026-78002 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (56th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-78002?
CVE-2026-78002 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-78002?
A fix for CVE-2026-78002 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-78002 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-78002

Explore →

Is Your Infrastructure Affected by CVE-2026-78002?

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