dahlia LogTape up to 1.3.10/2.0.13/2.1.4 Syslog syslog.ts escapeStructuredDataValue neutralization

Summaryinfo

A vulnerability has been found in dahlia LogTape up to 1.3.10/2.0.13/2.1.4 and classified as problematic. This impacts the function escapeStructuredDataValue of the file packages/syslog/src/syslog.ts of the component Syslog. Performing a manipulation results in neutralization. This vulnerability is identified as CVE-2026-54511. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability classified as problematic has been found in dahlia LogTape up to 1.3.10/2.0.13/2.1.4. This affects the function escapeStructuredDataValue of the file packages/syslog/src/syslog.ts of the component Syslog. The manipulation with an unknown input leads to a neutralization vulnerability. CWE is classifying the issue as CWE-707. The product does not ensure or incorrectly ensures that structured messages or data are well-formed and that certain security properties are met before being read from an upstream component or sent to a downstream component. This is going to have an impact on integrity. The summary by CVE is:

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.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-54511 since 06/15/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit.

Upgrading to version 1.3.11, 2.0.14 or 2.1.5 eliminates this vulnerability.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• dahlia

Name

• LogTape

Version

• 1.3.0
• 1.3.1
• 1.3.2
• 1.3.3
• 1.3.4
• 1.3.5
• 1.3.6
• 1.3.7
• 1.3.8
• 1.3.9
• 1.3.10
• 2.0.0
• 2.0.1
• 2.0.2
• 2.0.3
• 2.0.4
• 2.0.5
• 2.0.6
• 2.0.7
• 2.0.8
• 2.0.9
• 2.0.10
• 2.0.11
• 2.0.12
• 2.0.13
• 2.1.0
• 2.1.1
• 2.1.2
• 2.1.3
• 2.1.4

Website

• Product: https://github.com/dahlia/logtape/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion