🚨 [security] Update morgan 1.10.0 → 1.12.0 (minor)

[depfu]

---

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

---

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ morgan (1.10.0 → 1.12.0) · Repo · Changelog

Security Advisories 🚨

🚨 morgan vulnerable to Log Forging via unescaped Unicode line separators

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.

🚨 morgan vulnerable to Log Forging via unneutralized control characters in :remote-user

Impact

Morgan's :remote-user token extracts the Basic auth username from the Authorization header and writes it to the log stream without neutralizing control characters. An attacker can send a crafted Authorization: Basic header containing CR/LF characters to inject forged log lines, corrupting the one-request-per-line structure of access logs.

The built-in combined, common, default, and short formats are affected, as well as any custom format that includes :remote-user.

Patches

Users should upgrade to version 1.11.0.

Workarounds

Use a custom format string that does not include :remote-user.

Release Notes

1.12.0

What's Changed

• fix: upgrade http:// to https:// in README by @hanu-14 in #363
• build: bump github actions and dev dependencies by @sheplu in #369
• chore(ci): npm-publish via reusable workflows by @sheplu in #334
• docs: add ES modules import example by @aladi-debug in #352
• docs: fix README lint errors by @UlisesGascon in #373
• ci: use latest patch per Node.js major, add 23-26 by @UlisesGascon in #374
• feat: pass objects through to streams in objectMode by @UlisesGascon in #375
• feat: NO_COLOR env var removes color in dev format by @jonchurch in #377

New Contributors

• @hanu-14 made their first contribution in #363
• @sheplu made their first contribution in #369
• @aladi-debug made their first contribution in #352

Full Changelog: 1.11.0...1.12.0

1.11.0

What's Changed

• feat: add :pid token by @ganesh3367 in #329

Security Fix:

• Escape control characters in :remote-user token to prevent log injection
  • Fixes CVE-2026-5078 GHSA-4vj7-5mj6-jm8m

New Contributors

• @inigomarquinez made their first contribution in #291
• @jonchurch made their first contribution in #299
• @bjohansebas made their first contribution in #301
• @UlisesGascon made their first contribution in #300
• @ctcpip made their first contribution in #319
• @ganesh3367 made their first contribution in #329

Full Changelog: 1.10.0...1.11.0

1.10.1

What's Changed

• renaming simple to sample in readme by @ryhinchey in #237
• adding installation instructions to readme by @ryhinchey in #233
• chore: add support for OSSF scorecard reporting by @inigomarquinez in #291
• ci: replace travis with github actions by @inigomarquinez in #290
• docs: add example output for log formats by @jonchurch in #299
• ci: use ubuntu-latest by @bjohansebas in #301
• ci: apply OSSF Scorecard security best practices by @UlisesGascon in #300
• remove --bail by @jonchurch in #314
• ⬆️ bump on-headers by @ctcpip in #319

New Contributors

• @inigomarquinez made their first contribution in #291
• @jonchurch made their first contribution in #299
• @bjohansebas made their first contribution in #301
• @UlisesGascon made their first contribution in #300
• @ctcpip made their first contribution in #319

Full Changelog: 1.10.0...1.10.1

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 44 commits:

• 1.12.0 (#376)
• fix: escape all token values in log output
• feat: NO_COLOR env var removes color in dev format (#377)
• feat: pass objects through to streams in objectMode (#375)
• ci: use latest patch per Node.js major, add 23-26 (#374)
• docs: fix README lint errors (#373)
• docs: add ES modules import example (#352)
• chore(ci): npm-publish via reusable workflows (#334)
• build: bump github actions and dev dependencies (#369)
• docs: update link (#363)
• Release 1.11.0 (#350)
• Merge commit from fork
• build(deps): bump github/codeql-action from 4.32.4 to 4.35.2 (#346)
• build(deps): bump actions/upload-artifact from 7.0.0 to 7.0.1 (#347)
• build(deps): bump actions/upload-artifact from 5.0.0 to 7.0.0 (#338)
• build(deps): bump github/codeql-action from 3.29.7 to 4.32.4 (#337)
• build(deps): bump ossf/scorecard-action from 2.3.1 to 2.4.3 (#327)
• build(deps): bump actions/checkout from 4.1.1 to 6.0.1 (#324)
• build(deps): bump actions/upload-artifact from 4.3.1 to 4.6.2 (#307)
• build(deps): bump coverallsapp/github-action from 1.2.5 to 2.3.6 (#306)
• build(deps): bump on-finished from 2.3.0 to 2.4.1 (#312)
• test: fix flaky test that relied on interval timing (#331)
• chore: remove history.md from the published files (#330)
• feat: add :pid token (#329)
• build(deps): bump github/codeql-action from 2.23.2 to 3.29.5 (#323)
• chore: add funding to package.json (#322)
• fix: typo in url
• 🔖 1.10.1
• ⬆️ bump on-headers
• remove --bail (#314)
• ci: apply OSSF Scorecard security best practices (#300)
• ci: use ubuntu-latest (#301)
• docs: add example output for log formats (#299)
• ci: migra to GitHub actions (#290)
• ci: add support for OSSF scorecard reporting (#291)
• docs: add installation section
• docs: change simple to sample in example descriptions
• build: eslint-plugin-node@11.1.0
• build: eslint-plugin-import@2.20.2
• build: Node.js@13.12
• build: Node.js@10.20
• build: nyc@15.0.1
• build: eslint-plugin-node@10.0.0
• build: eslint-config-standard@14.1.1

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[depfu]

Closed in favor of #311.