CVE-2026-61548

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.9% (60th 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

Also known asEUVD-2026-83185 (ENISA EUVD)Source: ENISA EUVD

8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 8.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Rsyslog is a rocket-fast system for log processing. From 7.5.4 until 8.2606.0, the optional mmpstrucdata plugin's parseSD_PARAM function in plugins/mmpstrucdata/mmpstrucdata.c stores RFC5424 parameter values in a fixed pVal[32 * 1024] stack buffer and calls parsePARAM_VALUE without supplying the destination size. A remote unauthenticated attacker whose crafted RFC5424 message reaches an action using mmpstrucdata can provide a structured-data parameter larger than that buffer when MaxMessageSize permits it, causing an attacker-controlled stack overwrite. Deployments that do not install and use the plugin, or whose effective message-size limit remains below the required threshold, are not affected by this issue. The demonstrated impact is a crash and interruption of log collection; code execution is not demonstrated. This issue is fixed in version 8.2606.0.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/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)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.9% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.9%
EPSS %ILE
60th
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 (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 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.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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

September 18, 2026

Last Modified

September 24, 2026

Advisory Details (4)

Auto-updated Sep 18, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
GitHub release Patch Available

rsyslog 8.2606.0

Patch available: rsyslog/rsyslog v8.2606.0

https://github.com/rsyslog/rsyslog/releases/tag/v8.2606.0
GitHub commit Patch Available

commit bcda60a3692e (rsyslog/rsyslog)

Patch available: rsyslog/rsyslog v8.2606.0 (contains commit bcda60a3692e)

https://github.com/rsyslog/rsyslog/commit/bcda60a3692efdf0c8e44102528f5a0ebe0dec6d
GitHub pull request Patch Available

mmpstrucdata: support custom SD containers

Patch available: rsyslog/rsyslog v8.2606.0 (PR #6991 merged 2026-06-02)

https://github.com/rsyslog/rsyslog/pull/6991
GitHub advisoryMentions a patch (unverified)

mmpstrucdata stack buffer overflow with oversized RFC5424 structured data · Advisory · rsyslog/rsyslog · GitHub

https://github.com/rsyslog/rsyslog/security/advisories/GHSA-8qmr-c66f-g368

Vendor Advisories for CVE-2026-61548(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntursyslog-snmp (8.2512.0-1ubuntu4.1) @ resolute2026-10-28ubuntu

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.2606.0-3 (22 versions)
  • every version up to 8.2606.0-4: fixed in 8.2606.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 9× in last 7d / 65× 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 123 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 23 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-61548?
CVE-2026-61548 is a high-severity vulnerability; its CVE record was published on September 18, 2026. Rsyslog is a rocket-fast system for log processing. From 7.5.4 until 8.2606.0, the optional mmpstrucdata plugin's parseSD_PARAM function in plugins/mmpstrucdata/mmpstrucdata.c stores RFC5424 parameter values in a fixed pVal[32 * 1024] stack buffer and calls parsePARAM_VALUE without supplying the…
When was the CVE record for CVE-2026-61548 published?
The CVE record for CVE-2026-61548 was published on September 18, 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 September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-61548 actively exploited?
CVE-2026-61548 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (60th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61548?
CVE-2026-61548 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-61548?
A fix for CVE-2026-61548 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-61548 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-61548

Explore →

Is Your Infrastructure Affected by CVE-2026-61548?

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

Book a Demo →Browse All CVEs