CVE-2026-5078

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 74% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

A fix is available — apply it.

Impact: The morgan logging middleware's :remote-user token extracts the Basic auth username from the Authorization request header and writes it to the log stream without neutralizing control characters. An unauthenticated attacker can send a crafted Authorization Basic header containing CR or LF bytes to inject forged log lines, breaking the one-request-per-line structure of access logs and enabling log forgery against downstream log consumers. The built-in combined, common, default, and short formats are affected, as well as any custom format that references :remote-user. Affected versions: morgan 1.2.0 through 1.10.1. Patches: upgrade to morgan 1.11.0, which neutralizes control characters in the :remote-user token output. Workarounds: use a custom format string that does not include :remote-user.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

June 3, 2026

Last Modified

July 22, 2026

Advisory Details (2)

Auto-updated Jun 16, 2026
Patch available. Sources: github.
github Patch Available

morgan vulnerable to Log Forging via unneutralized control characters in :remote-user · Advisory · expressjs/morgan · GitHub

https://github.com/expressjs/morgan/security/advisories/GHSA-4vj7-5mj6-jm8m
generic

Security Advisories | OpenJS Foundation CVE Numbering Authority

https://cna.openjsf.org/security-advisories.html

Vendor Advisories for CVE-2026-5078(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatnodejs22-main-22.23.1-2.1.hum12026-07-12redhat
redhatnodejs24-main-24.18.0-0.3.hum12026-07-11redhat
redhatnodejs26-main-26.5.0-1.3.hum12026-07-10redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
node-morgan1.10.0+~1.9.3-1, 1.10.1+~1.9.10-1, 1.12.0+~1.9.10-1——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-morgan1.10.0+~1.9.3-1, 1.10.1+~1.9.10-1, 1.12.0+~1.9.10-1——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-morgan1.10.0+~1.9.3-1, 1.10.1+~1.9.10-11.12.0+~1.9.10-1—
npm(1)
PackageVulnerable rangeFixed inDependents
morgan—1.11.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 176 total refreshes for this CVE.

  1. 2026-09-16 05:15 UTCEPSS rescore
  2. 2026-09-15 03:11 UTCEPSS rescore
  3. 2026-09-14 05:39 UTCEG score recompute
  4. 2026-09-14 05:39 UTCVendor advisory
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-12 23:36 UTCOSV refresh
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-10 09:35 UTCEPSS rescore
  9. 2026-09-08 22:01 UTCEPSS rescore
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-04 05:07 UTCEPSS rescore
  13. 2026-09-02 14:12 UTCEPSS rescore
  14. 2026-09-01 13:54 UTCEPSS rescore
  15. 2026-09-01 04:40 UTCEPSS rescore
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-30 01:22 UTCEPSS rescore
  18. 2026-08-28 21:42 UTCEPSS rescore
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-25 03:42 UTCEG score recompute
  23. 2026-08-25 03:42 UTCVendor advisory
  24. 2026-08-23 13:36 UTCEG score recompute
  25. 2026-08-23 13:36 UTCVendor advisory
Show 75 more
  1. 2026-08-23 00:19 UTCEPSS rescore
  2. 2026-08-21 23:49 UTCEPSS rescore
  3. 2026-08-21 14:43 UTCEG score recompute
  4. 2026-08-21 14:43 UTCVendor advisory
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-20 10:07 UTCEG score recompute
  7. 2026-08-20 10:07 UTCVendor advisory
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-17 13:47 UTCEPSS rescore
  11. 2026-08-16 16:26 UTCEG score recompute
  12. 2026-08-16 16:26 UTCVendor advisory
  13. 2026-08-16 14:56 UTCEPSS rescore
  14. 2026-08-15 14:53 UTCEG score recompute
  15. 2026-08-15 14:53 UTCVendor advisory
  16. 2026-08-15 01:30 UTCEPSS rescore
  17. 2026-08-14 11:47 UTCEG score recompute
  18. 2026-08-14 11:47 UTCVendor advisory
  19. 2026-08-13 22:00 UTCEPSS rescore
  20. 2026-08-13 10:14 UTCEG score recompute
  21. 2026-08-13 10:14 UTCVendor advisory
  22. 2026-08-12 13:51 UTCEPSS rescore
  23. 2026-08-12 08:38 UTCEG score recompute
  24. 2026-08-12 08:38 UTCVendor advisory
  25. 2026-08-11 06:00 UTCEG score recompute
  26. 2026-08-11 06:00 UTCVendor advisory
  27. 2026-08-11 00:00 UTCEPSS rescore
  28. 2026-08-10 04:27 UTCEG score recompute
  29. 2026-08-10 04:27 UTCVendor advisory
  30. 2026-08-09 13:46 UTCEPSS rescore
  31. 2026-08-09 02:54 UTCEG score recompute
  32. 2026-08-09 02:54 UTCVendor advisory
  33. 2026-08-08 16:37 UTCEPSS rescore
  34. 2026-08-08 01:21 UTCEG score recompute
  35. 2026-08-08 01:21 UTCVendor advisory
  36. 2026-08-06 23:47 UTCEG score recompute
  37. 2026-08-06 23:47 UTCVendor advisory
  38. 2026-08-06 13:47 UTCEPSS rescore
  39. 2026-08-05 21:04 UTCEG score recompute
  40. 2026-08-05 21:04 UTCVendor advisory
  41. 2026-08-05 19:17 UTCEPSS rescore
  42. 2026-08-04 19:30 UTCEG score recompute
  43. 2026-08-04 19:30 UTCVendor advisory
  44. 2026-08-04 15:10 UTCEPSS rescore
  45. 2026-08-04 10:39 UTCEPSS rescore
  46. 2026-08-03 16:15 UTCEG score recompute
  47. 2026-08-03 16:15 UTCVendor advisory
  48. 2026-08-03 10:36 UTCEPSS rescore
  49. 2026-08-02 14:42 UTCEG score recompute
  50. 2026-08-02 14:42 UTCVendor advisory
  51. 2026-08-02 02:27 UTCEPSS rescore
  52. 2026-08-01 13:08 UTCEG score recompute
  53. 2026-08-01 13:08 UTCVendor advisory
  54. 2026-08-01 04:16 UTCEPSS rescore
  55. 2026-07-31 05:33 UTCEG score recompute
  56. 2026-07-31 05:33 UTCVendor advisory
  57. 2026-07-30 16:28 UTCEPSS rescore
  58. 2026-07-30 01:30 UTCEPSS rescore
  59. 2026-07-30 01:30 UTCEPSS rescore
  60. 2026-07-29 10:26 UTCEG score recompute
  61. 2026-07-29 10:26 UTCVendor advisory
  62. 2026-07-28 15:37 UTCEPSS rescore
  63. 2026-07-28 03:33 UTCEG score recompute
  64. 2026-07-28 03:33 UTCVendor advisory
  65. 2026-07-27 14:14 UTCEPSS rescore
  66. 2026-07-26 22:42 UTCEG score recompute
  67. 2026-07-26 22:42 UTCVendor advisory
  68. 2026-07-26 14:54 UTCEPSS rescore
  69. 2026-07-26 14:54 UTCEPSS rescore
  70. 2026-07-25 14:18 UTCEPSS rescore
  71. 2026-07-25 14:18 UTCEPSS rescore
  72. 2026-07-24 14:18 UTCEPSS rescore
  73. 2026-07-24 14:18 UTCEPSS rescore
  74. 2026-07-23 14:18 UTCEPSS rescore
  75. 2026-07-23 14:18 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-5078?
CVE-2026-5078 is a medium vulnerability published on June 3, 2026. Impact: The morgan logging middleware's :remote-user token extracts the Basic auth username from the Authorization request header and writes it to the log stream without neutralizing control characters. An unauthenticated attacker can send a crafted Authorization Basic header containing CR or LF…
When was CVE-2026-5078 disclosed?
CVE-2026-5078 was first published in the National Vulnerability Database on June 3, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-5078 actively exploited?
CVE-2026-5078 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 73.7% of all scored CVEs.
What is the CVSS score of CVE-2026-5078?
CVE-2026-5078 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-5078?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-5078, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-5078

Explore →

Is Your Infrastructure Affected by CVE-2026-5078?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs