CVE-2026-54511Public exploitNetwork attack vector

Syslog record forgery via unescaped structured data

Published Aug 26, 2026 · Updated Aug 26, 2026

Log injection in LogTape @logtape/syslog before 1.3.11, 2.0.0 through 2.0.13, and 2.1.0 through 2.1.4 allows remote attackers to forge syslog records. escapeStructuredDataValue() leaves C0 control bytes in values, and formatStructuredData() emits keys without enforcing the RFC 5424 SD-NAME grammar. Exploitation requires the non-default includeStructuredData setting and attacker-controlled properties; injected frames can impersonate arbitrary hosts, applications, processes, facilities, or severity levels in downstream collectors and SIEMs.

CVSS severity8.6
High
EPSS probability0.31%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Log injection in LogTape @logtape/syslog before 1.3.11, 2.0.0 through 2.0.13, and 2.1.0 through 2.1.4 allows remote attackers to forge syslog records. escapeStructuredDataValue() leaves C0 control bytes in values, and formatStructuredData() emits keys without enforcing the RFC 5424 SD-NAME grammar. Exploitation requires the non-default includeStructuredData setting and attacker-controlled properties; injected frames can impersonate arbitrary hosts, applications, processes, facilities, or severity levels in downstream collectors and SIEMs.

The record

CVE
CVE-2026-54511
Published
Aug 26, 2026
Updated
Aug 26, 2026
Vendor
dahlia
Product
LogTape
Classifications
CWE-117, CWE-93, T1036
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 26, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 26, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 1.3.11
  2. Affected versionversion=>= 2.0.0, < 2.0.14
  3. Affected versionversion=>= 2.1.0, < 2.1.5

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

dahlia · LogTapeversion=< 1.3.11; version=>= 2.0.0, < 2.0.14; version=>= 2.1.0, < 2.1.5

Published CVSS scores

8.6GitHubCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-117Improper Output Neutralization for Logs
CWE-93Improper Neutralization of CRLF Sequences ('CRLF Injection')
T1036Masquerading

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo