VulnerabilityPublished 28 Sep 2026

CVE-2026-87859: morgan vulnerable to Log Injection via unescaped double quote in quoted log fields

Affects morganSource GCVE Database

Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 1.12.1 when convenient.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.12.1

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade morgan to 1.12.1.

Affected software

Product	Affected	Fixed in
npmmorgan	Affected <1.12.1	Fixed in 1.12.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade Morgan to version 1.12.1, where the vulnerability is fixed. No other workarounds are indicated. The patch is officially available and addresses the issue.

Description

Morgan versions prior to 1.12.1 are vulnerable to log injection via unescaped double quotes in quoted log fields. This vulnerability allows an attacker controlling certain request fields to inject double quotes that prematurely close quoted fields in the Apache combined log format, enabling forged log entries. The issue affects the combined, common, default, and any custom formats that quote tokens. A fix is available in version 1.12.1.

Impact

An attacker can manipulate log entries by injecting double quotes into quoted log fields, potentially forging log records. This can mislead log analysis, obscure malicious activity, or facilitate log-based attacks. The vulnerability does not impact confidentiality or availability but affects the integrity of log data.

Summary

Morgan's access log escaping neutralizes control characters, Unicode line separators, and backslashes but does not escape the double quote character (0x22), which is used as a field delimiter in the Apache combined log format. An attacker controlling quoted fields such as :user-agent, :referrer, request URL, or Basic auth :remote-user can inject a double quote to prematurely close the field and forge additional log fields. This vulnerability affects multiple log formats and represents an incomplete fix of previous CVEs (2026-5078 and 2026-15603). The issue is addressed in Morgan version 1.12.1.

CWE-117Improper Output Neutralization for Logs (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A09:2025: Security Logging & Alerting Failures (opens in a new tab)
The product constructs a log message from external input, but it does not neutralize or incorrectly neutralizes special elements when the message is written to a log file.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Implementation · Output Encoding
Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8.
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP Cheat Sheets
Logging (opens in a new tab)
Content Security Policy (opens in a new tab)
Application Logging Vocabulary (opens in a new tab)
OWASP ASVS 4.0.3
V7.3.1 (opens in a new tab)
V14.4.6 (opens in a new tab)
V14.4.4 (opens in a new tab)
Attack patterns
Audit Log Manipulation (opens in a new tab)
Web Server Logs Tampering (opens in a new tab)
Log Injection-Tampering-Forging (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Nov 2026, 09:43 UTC

WeaknessesCWE-117

Technical details

References

Community reviews

Related threats