CVE-2026-19654

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.5% (44th 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.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A unauthenticated remote peer may lead rsyslogd to crash due to a flaw in the optional imptcp module. A crafted input sequence during oversize-frame recovery can cause an invalid internal message length and terminate rsyslogd. No confidentiality or integrity impact, privilege escalation, or code execution has been identified. imtcp and the default imptcp framing modes are not affected.

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.5% × 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.5%
EPSS %ILE
44th
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.5% 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 12, 2026

Last Modified

October 19, 2026

Advisory Details (2)

Auto-updated Aug 12, 2026
Patch available. Sources: redhat.
Red Hat

2502868 – (CVE-2026-19654) CVE-2026-19654 rsyslog: A configuration-dependent issue in rsyslog's optional imptcp input module can allow an unauthenticated remote peer to crash rsyslogd

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

CVE-2026-19654 - 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-19654

Vendor Advisories for CVE-2026-19654(8)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrsyslog-0:8.2102.0-15.el8_10.32026-10-12redhat
redhatrhui5/haproxy-rhel9:17902419002026-09-24redhat
redhatrsyslog-0:8.2510.0-5.el10_2.12026-09-15redhat
redhatrsyslog-0:8.2510.0-2.el9_8.12026-09-15redhat
redhatrsyslog-0:8.2412.0-1.el10_0.12026-09-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

(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
  • every version up to 8.2504.0-1+deb13u1: fixed in 8.2504.0-1+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
rsyslog8.2504.0-1 ... 8.2606.0-4 (23 versions)
  • every version up to 8.2608.0-1: fixed in 8.2608.0-1
—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-19654?
CVE-2026-19654 is a high-severity vulnerability; its CVE record was published on August 12, 2026. A unauthenticated remote peer may lead rsyslogd to crash due to a flaw in the optional imptcp module. A crafted input sequence during oversize-frame recovery can cause an invalid internal message length and terminate rsyslogd. No confidentiality or integrity impact, privilege escalation, or code…
When was CVE-2026-19654 made public?
CVE-2026-19654 was made public on July 22, 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 12, 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-19654 actively exploited?
CVE-2026-19654 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-19654?
CVE-2026-19654 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-19654?
A fix for CVE-2026-19654 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-19654 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-19654

Explore →

Is Your Infrastructure Affected by CVE-2026-19654?

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

Book a Demo →Browse All CVEs