fix(deps): update dependency morgan to v1.12.1 [security]

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
morgan	1.10.1 → 1.12.1

---

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).

---

morgan vulnerable to Log Forging via unescaped Unicode line separators

CVE-2026-15603 / GHSA-jxfw-x594-9x9m

More information

Details

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.

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-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/releases/tag/1.12.0
• https://github.com/advisories/GHSA-jxfw-x594-9x9m

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

---

morgan vulnerable to Log Injection via unescaped double quote in quoted log fields

CVE-2026-87859 / GHSA-9f6g-j8ch-79g4

More information

Details

Impact

Morgan writes attacker-controlled request data to the access log. Its escaping (added in 1.11.0 and 1.12.0) neutralizes control characters, the Unicode line separators, and backslash, but not the double quote (0x22), which is the field delimiter of the Apache combined log format morgan emits. An attacker who controls a quoted field (:user-agent, :referrer, the request URL, or the Basic auth :remote-user) can inject a double quote to close the field early and forge additional fields in the log record. The combined, common, and default formats, and any custom format that quotes a token, are affected. This is an incomplete fix of CVE-2026-5078 and CVE-2026-15603.

Patches

Users should upgrade to version 1.12.1.

Workarounds

Update to version 1.12.1.

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-9f6g-j8ch-79g4
• https://nvd.nist.gov/vuln/detail/CVE-2026-87859
• https://github.com/expressjs/morgan/commit/4b695edf967ce179cdf4009fe8cddd184b7511ee
• https://cna.openjsf.org/security-advisories.html
• https://github.com/expressjs/morgan/releases/tag/1.12.1
• https://github.com/advisories/GHSA-9f6g-j8ch-79g4

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

---

Release Notes

expressjs/morgan (morgan)

v1.12.1

Compare Source

======

• Security fix for CVE-2026-87859(GHSA-9f6g-j8ch-79g4)

v1.12.0

Compare Source

======

• Security fix for CVE-2026-15603(GHSA-jxfw-x594-9x9m)
• Allow format functions to return objects for streams in objectMode
• Respect the NO_COLOR environment variable in the dev format

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

---

Configuration

📅 Schedule: (UTC)

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates 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: 08-node-express-uploading/package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: multer-storage-cloudinary@4.0.0
npm ERR! Found: cloudinary@2.7.0
npm ERR! node_modules/cloudinary
npm ERR!   cloudinary@"2.7.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer cloudinary@"^1.21.0" from multer-storage-cloudinary@4.0.0
npm ERR! node_modules/multer-storage-cloudinary
npm ERR!   multer-storage-cloudinary@"4.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: cloudinary@1.41.3
npm ERR! node_modules/cloudinary
npm ERR!   peer cloudinary@"^1.21.0" from multer-storage-cloudinary@4.0.0
npm ERR!   node_modules/multer-storage-cloudinary
npm ERR!     multer-storage-cloudinary@"4.0.0" 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-10-13T17_28_07_605Z-debug-0.log