Approved changes feed: RSS · Atom
cpe:2.3:a:morgan:morgan:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Morgan (82dcd1a0-e6cb-59bc-bc9e-b86617bb9884) |
|---|---|
| Product | Morgan (3be7cc05-4252-506f-813a-cfbb100a2234) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-87859 |
vulnerable | 2026-09-16 04:33:01.253510 |
morgan vulnerable to Log Injection via unescaped double quote in quoted log fields
MEDIUM (5.3)
morgan is an HTTP request logger middleware for Node.js. In versions before 1.12.1, its escapeLogField() function does not escape the double quote character, which delimits the quoted fields of the Apache combined log format that morgan emits. An unauthenticated remote attacker who controls a value written to a quoted field, such as the User-Agent or Referer header, can include a double quote to close that field early, so a log consumer that parses the log by field position reads attacker-supplied text as the following field. In the built-in formats this makes the recorded value differ from the value that was sent, and in custom formats that quote an attacker-controlled token before a server-controlled one it can forge values such as the response status. No newline is injected, so record separation stays intact. The issue is fixed in morgan 1.12.1, which escapes the double quote. Users should upgrade to morgan 1.12.1 or later.
Published: 2026-09-11T09:15:19.109Z
Updated: 2026-09-11T11:32:10.246Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-5078 |
vulnerable | 2026-06-08 08:07:02.967986 |
morgan vulnerable to Log Forging via unneutralized control characters in :remote-user
MEDIUM (5.3)
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.
Published: 2026-06-03T05:56:49.512Z
Updated: 2026-06-03T13:19:32.922Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.