Update dependency morgan to v1.11.0 [SECURITY]

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
morgan	1.10.0 → 1.11.0

---

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

CVE-2026-5078 / GHSA-4vj7-5mj6-jm8m

More information

Details

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.

Severity

• CVSS Score: 5.3 / 10 (Medium)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

References

• https://github.com/expressjs/morgan/security/advisories/GHSA-4vj7-5mj6-jm8m
• https://nvd.nist.gov/vuln/detail/CVE-2026-5078
• https://cna.openjsf.org/security-advisories.html
• https://github.com/advisories/GHSA-4vj7-5mj6-jm8m

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

expressjs/morgan (morgan)

v1.11.0

Compare Source

===================

• add :pid token

Security Fix:

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

v1.10.1

Compare Source

===================

• deps: on-headers@~1.1.0
  • Fix CVE-2025-7339 (GHSA-76c9-3jph-rj3q)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: mongoose-auto-increment@5.0.1
npm ERR! Found: mongoose@5.13.13
npm ERR! node_modules/mongoose
npm ERR!   mongoose@"5.13.13" from the root project
npm ERR!   peer mongoose@"*" from mongoose-legacy-pluralize@1.0.2
npm ERR!   node_modules/mongoose-legacy-pluralize
npm ERR!     mongoose-legacy-pluralize@"1.0.2" from mongoose@5.13.13
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer mongoose@"^4.1.12" from mongoose-auto-increment@5.0.1
npm ERR! node_modules/mongoose-auto-increment
npm ERR!   mongoose-auto-increment@"5.0.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: mongoose@4.13.21
npm ERR! node_modules/mongoose
npm ERR!   peer mongoose@"^4.1.12" from mongoose-auto-increment@5.0.1
npm ERR!   node_modules/mongoose-auto-increment
npm ERR!     mongoose-auto-increment@"5.0.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-07-11T01_15_41_153Z-debug-0.log