CVE-2026-54511

HIGHPre-NVD 8.68.6
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (39th 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
8.6EG
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: 8.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

LogTape is an unobtrusive logging library. Prior to 1.3.11, 2.0.14, and 2.1.5, the @logtape/syslog package's escapeStructuredDataValue() function in packages/syslog/src/syslog.ts does not neutralize C0 control characters from U+0000 through U+001F in structured data values, and formatStructuredData() inserts property keys without validating the RFC 5424 SD-NAME grammar. When includeStructuredData is true, an attacker-controlled newline can terminate an RFC 6587 non-transparent TCP syslog frame and make following bytes appear as a forged RFC 5424 record, while a key containing a closing bracket or other forbidden character can terminate or corrupt the structured-data element. Applications that forward attacker-controlled property values or keys can therefore allow forged records with arbitrary hosts, applications, process identifiers, facilities, or severity levels, undermining downstream collector and SIEM integrity. This issue is fixed in versions 1.3.11, 2.0.14, and 2.1.5.

CVSS v3
8.6
EG Score
8.6HIGHmedium confidence
EG Risk
54
EG Risk 54/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)
Severity86% × 45%
The EG Score, 8.6 of 10.
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
39th
KEV
Not listed

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 26, 2026

Last Modified

September 9, 2026

Advisory Details (2)

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

@logtape/syslog: syslog log injection via unescaped control characters and unvalidated SD-NAME keys · Advisory · dahlia/logtape · GitHub

https://github.com/dahlia/logtape/security/advisories/GHSA-8h6h-x5pq-56fq
GitHub commit

commit 7a6e5b9ddf79 (dahlia/logtape)

Fix landed in dahlia/logtape commit 7a6e5b9ddf79 — awaiting tagged release

https://github.com/dahlia/logtape/commit/7a6e5b9ddf7915edfff78fa129bc17c979b2a623

Vendor Advisories for CVE-2026-54511(1)

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

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@logtape/syslog—
  • 2.1.0 up to 2.1.5: fixed in 2.1.5
  • 2.0.0 up to 2.0.14: fixed in 2.0.14
  • every version up to 1.3.11: fixed in 1.3.11
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 54× 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.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54511?
CVE-2026-54511 is a high-severity vulnerability; its CVE record was published on August 26, 2026. LogTape is an unobtrusive logging library. Prior to 1.3.11, 2.0.14, and 2.1.5, the @logtape/syslog package's escapeStructuredDataValue() function in packages/syslog/src/syslog.ts does not neutralize C0 control characters from U+0000 through U+001F in structured data values, and…
When was the CVE record for CVE-2026-54511 published?
The CVE record for CVE-2026-54511 was published on August 26, 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 9, 2026; the record at its source may have been updated since.
Is CVE-2026-54511 actively exploited?
CVE-2026-54511 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54511?
CVE-2026-54511 has a CVSS base score of 8.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54511?
A fix for CVE-2026-54511 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54511 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-54511

Explore →

Is Your Infrastructure Affected by CVE-2026-54511?

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

Book a Demo →Browse All CVEs