CVE-2026-54511

published 26 Aug 2026 · updated 27 Aug 2026

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

8.6HighCVSS 8.6EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
dahlia<1.3.11, >=2.0.0 <2.0.14, >=2.1.0 <2.1.5

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-54511 severity on Zeptric[![CVE-2026-54511](https://zeptric.io/badge/cve/CVE-2026-54511.svg)](https://zeptric.io/cve/CVE-2026-54511)