Answer in brief
CVE-2026-54511 records a High severity (CVSS 8.6) vulnerability in @logtape/syslog: syslog log injection via unescaped control characters and unvalidated SD-NAME keys. The current sources do not mark it as known exploited. The current feed maps dahlia/logtape (generic), @logtape/syslog (npm), @logtape/syslog (npm), @logtape/syslog (npm). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.6. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps dahlia/logtape (generic), @logtape/syslog (npm), @logtape/syslog (npm), @logtape/syslog (npm). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| dahlia/logtapegeneric | < 1.3.11 || >= 2.0.0, < 2.0.14 || >= 2.1.0, < 2.1.5 | Not reported |
| @logtape/syslognpm | >=2.1.0,<=2.1.4 | 2.1.5 |
| @logtape/syslognpm | >=2.0.0,<2.0.14 | 2.0.14 |
| @logtape/syslognpm | <1.3.11 | 1.3.11 |
Published upstream
Aug 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 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 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.
Quoted source text, attributed separately from HOL analysis.