morgan vulnerable to Log Forging via unescaped Unicode line separators
cve-program · CVE-2026-15603
Publishedmorgan is an HTTP request logger middleware for Node.js. In versions prior to 1.12.0, the internal helper that escapes log token values did not neutralize the Unicode line separator characters U+0085 (Next Line), U+2028 (Line Separator), and U+2029 (Paragraph Separator). An unauthenticated remote client can place these characters in an attacker-controlled log token, for example a Basic auth username surfaced through the remote-user token, so that Unicode-aware downstream log processing splits a single request log into multiple logical records. This is a log forging issue (CWE-117) and an incomplete-fix follow-up to CVE-2026-5078, which only addressed ASCII control characters. The issue is fixed in morgan 1.12.0, which extends the escaping set to cover these Unicode line separators. Upgrade to morgan 1.12.0 to remediate.
Read the publisher's advisoryeuvd · EUVD-2026-67720
Publishedmorgan is an HTTP request logger middleware for Node.js. In versions prior to 1.12.0, the internal helper that escapes log token values did not neutralize the Unicode line separator characters U+0085 (Next Line), U+2028 (Line Separator), and U+2029 (Paragraph Separator). An unauthenticated remote client can place these characters in an attacker-controlled log token, for example a Basic auth username surfaced through the remote-user token, so that Unicode-aware downstream log processing splits a single request log into multiple logical records. This is a log forging issue (CWE-117) and an incomplete-fix follow-up to CVE-2026-5078, which only addressed ASCII control characters. The issue is fixed in morgan 1.12.0, which extends the escaping set to cover these Unicode line separators. Upgrade to morgan 1.12.0 to remediate.
Read the publisher's advisorynvd · CVE-2026-15603
Publishedmorgan is an HTTP request logger middleware for Node.js. In versions prior to 1.12.0, the internal helper that escapes log token values did not neutralize the Unicode line separator characters U+0085 (Next Line), U+2028 (Line Separator), and U+2029 (Paragraph Separator). An unauthenticated remote client can place these characters in an attacker-controlled log token, for example a Basic auth username surfaced through the remote-user token, so that Unicode-aware downstream log processing splits a single request log into multiple logical records. This is a log forging issue (CWE-117) and an incomplete-fix follow-up to CVE-2026-5078, which only addressed ASCII control characters. The issue is fixed in morgan 1.12.0, which extends the escaping set to cover these Unicode line separators. Upgrade to morgan 1.12.0 to remediate.
Read the publisher's advisoryosv · GHSA-jxfw-x594-9x9m
Published### Impact Morgan writes attacker-controlled request data to the access log through its tokens. The 1.11.0 fix neutralizes C0 control characters, DEL, and backslash, but it does not escape the Unicode line separators `U+0085` (NEL), `U+2028` (LINE SEPARATOR), or `U+2029` (PARAGRAPH SEPARATOR). These code points are reachable through several tokens, including the request URL (`:url`), request headers such as `:user-agent` and `:referrer`, arbitrary `:req[header]` values, and the Basic auth username (`:remote-user`). NEL is valid `obs-text` in HTTP header values, so an attacker can place it in an ordinary request header. When such a value is logged, the raw code points survive into the emitted access-log record, and downstream ECMAScript-aware or Unicode-aware log processing splits the single physical record into multiple logical records. This allows an attacker to forge log entries. The built-in `combined`, `common`, `default`, and `short` formats are affected, as well as any custom format. This is an incomplete fix of CVE-2026-5078. ### Patches Users should upgrade to version 1.12.0. ### Workarounds None. The affected values include the request URL and request headers, which are core to access logging, so there is no practical format-based mitigation. Upgrade to 1.12.0.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-15603 · CVE overview and exploitation status
cve-program · CVE-2026-15603
- https://github.com/expressjs/morgan/security/advisories/GHSA-jxfw-x594-9x9m
- https://cna.openjsf.org/security-advisories.html
euvd · EUVD-2026-67720
- https://github.com/expressjs/morgan/security/advisories/GHSA-jxfw-x594-9x9m
- https://cna.openjsf.org/security-advisories.html
nvd · CVE-2026-15603
- https://cna.openjsf.org/security-advisories.html
- https://github.com/expressjs/morgan/security/advisories/GHSA-jxfw-x594-9x9m
osv · GHSA-jxfw-x594-9x9m
- https://github.com/expressjs/morgan/security/advisories/GHSA-jxfw-x594-9x9m
- https://nvd.nist.gov/vuln/detail/CVE-2026-15603
- https://github.com/expressjs/morgan/commit/fbf93833186920cc39bb19b247e4a86b61bef4fe
- https://cna.openjsf.org/security-advisories.html
- https://github.com/expressjs/morgan
- https://github.com/expressjs/morgan/releases/tag/1.12.0
Related changes
Linked by CVE identifierNo related changes are available here.