Evidence used
- No CISA KEV confirmation is currently recorded.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 0.29% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-15603High confidence
morgan vulnerable to Log Forging via unescaped Unicode line separators
morgan · morgan
Official source article: GitHub GHSA-JXFW-X594-9X9M ↗. Check the applicable product and release in the original source.
5.3MediumCVSS 3.1
Patch only the product branches with a verified fix
Fix availability varies by productMedium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 44 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:Medium, unchanged from published severity.unchanged
Compensating controls
- Apply the linked authoritative mitigation while planning the permanent fix.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs morgan morgan and falls inside the recorded affected range.
- Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 44 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Red Hat Product Security: 42 affected or under-investigation product states without a fixed product state in the same current advisory
- Debian Security Tracker: 2 affected package states with no published fix
Distribution package intelligence
5 package statesRelease-specific package status
Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Package result overrides the generic status
BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 2 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | node-morgan | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian bookwormbookworm · source | node-morgan | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian forkyforky · source | node-morgan | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.12.0+~1.9.10-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian sidsid · source | node-morgan | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.12.0+~1.9.10-1 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | node-morgan | Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 6 Oct 2026 |
Open-source package ranges1 source-attributed range
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| npmmorgan | < 1.12.0 | 1.12.0 | GitHub advisory ↗upstream repository advisory · 8 Sep 2026 |
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2026-15603 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitymorgan: morgan: Log Forging via unescaped Unicode line separators
The vendor explicitly identifies these products as affected by this CVE.
- cryostat/cryostat-openshift-console-plugin-rhel9 as a component of Cryostat 4
- linux-sgx.src as a component of Red Hat Enterprise Linux 10
- nodejs as a component of Red Hat Enterprise Linux 10
- nodejs-devel as a component of Red Hat Enterprise Linux 10
- nodejs-docs as a component of Red Hat Enterprise Linux 10
- nodejs-full-i18n as a component of Red Hat Enterprise Linux 10
- nodejs-libs as a component of Red Hat Enterprise Linux 10
- nodejs-npm as a component of Red Hat Enterprise Linux 10
- nodejs22.src as a component of Red Hat Enterprise Linux 10
- nodejs24 as a component of Red Hat Enterprise Linux 10
- nodejs24-devel as a component of Red Hat Enterprise Linux 10
- nodejs24-docs as a component of Red Hat Enterprise Linux 10
- Summary
- A flaw was found in morgan, an HTTP request logger middleware for Node.js. An unauthenticated remote client can inject specific Unicode line separator characters into log token values. This manipulation can cause downstream log processing systems to misinterpret a single log entry as multiple records, leading to log forging. Log forging allows an attacker to inject false entries into log files, potentially obscuring malicious activities or hindering incident response.
- Remediation
- Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 44 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
morgan is an HTTP request logger middleware for Node.js. In versions prior to 1.12.0, the internal helper that escapes log token values did not neutralize the Unicode line separator characters U+0085 (Next Line), U+2028 (Line Separator), and U+2029 (Paragraph Separator). An unauthenticated remote client can place these characters in an attacker-controlled log token, for example a Basic auth username surfaced through the remote-user token, so that Unicode-aware downstream log processing splits a single request log into multiple logical records. This is a log forging issue (CWE-117) and an incomplete-fix follow-up to CVE-2026-5078, which only addressed ASCII control characters. The issue is fixed in morgan 1.12.0, which extends the escaping set to cover these Unicode line separators. Upgrade to morgan 1.12.0 to remediate.
What
morgan is an HTTP request logger middleware for Node.js. In versions prior to 1.12.0, the internal helper that escapes log token values did not neutralize the Unicode line separator characters U+0085 (Next Line), U+2028 (Line Separator), and U+2029 (Paragraph Separator). An unauthenticated remote client can place these characters in an attacker-controlled log token, for example a Basic auth username surfaced through the remote-user token, so that Unicode-aware downstream log processing splits a single request log into multiple logical records. This is a log forging issue (CWE-117) and an incomplete-fix follow-up to CVE-2026-5078, which only addressed ASCII control characters. The issue is fixed in morgan 1.12.0, which extends the escaping set to cover these Unicode line separators. Upgrade to morgan 1.12.0 to remediate.
Why
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.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
morgan is an HTTP request logger middleware for Node.js. In versions prior to 1.12.0, the internal helper that escapes log token values did not neutralize the Unicode line separator characters U+0085 (Next Line), U+2028 (Line Separator), and U+2029 (Paragraph Separator). An unauthenticated remote client can place these characters in an attacker-controlled log token, for example a Basic auth username surfaced through the remote-user token, so that Unicode-aware downstream log processing splits a single request log into multiple logical records. This is a log forging issue (CWE-117) and an incomplete-fix follow-up to CVE-2026-5078, which only addressed ASCII control characters. The issue is fixed in morgan 1.12.0, which extends the escaping set to cover these Unicode line separators. Upgrade to morgan 1.12.0 to remediate.
Why
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.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Improper Output Neutralization for Logs → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-117 ↗
CWE-117: Improper Output Neutralization for Logs. 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.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.ILowIntegrity impact: A successful attack can cause a limited loss.ANoneAvailability impact: No direct loss is represented by this metric.- Post-exploitation / living off the land
- Stolen credentials, tokens and legitimate administration functions may provide continued access without deploying a large custom toolset.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Affected
- cryostat/cryostat-openshift-console-plugin-rhel9 as a component of Cryostat 4
- linux-sgx.src as a component of Red Hat Enterprise Linux 10
- nodejs as a component of Red Hat Enterprise Linux 10
- nodejs-devel as a component of Red Hat Enterprise Linux 10
- nodejs-docs as a component of Red Hat Enterprise Linux 10
- nodejs-full-i18n as a component of Red Hat Enterprise Linux 10
- nodejs-libs as a component of Red Hat Enterprise Linux 10
- nodejs-npm as a component of Red Hat Enterprise Linux 10
- nodejs22.src as a component of Red Hat Enterprise Linux 10
- nodejs24 as a component of Red Hat Enterprise Linux 10
- nodejs24-devel as a component of Red Hat Enterprise Linux 10
- nodejs24-docs as a component of Red Hat Enterprise Linux 10
- nodejs24-full-i18n as a component of Red Hat Enterprise Linux 10
- nodejs24-libs as a component of Red Hat Enterprise Linux 10
- nodejs24-npm as a component of Red Hat Enterprise Linux 10
- nodejs24.src as a component of Red Hat Enterprise Linux 10
- nodejs26.src as a component of Red Hat Enterprise Linux 10
- sgx-common as a component of Red Hat Enterprise Linux 10
- sgx-libs as a component of Red Hat Enterprise Linux 10
- sgx-mpa as a component of Red Hat Enterprise Linux 10
- sgx-pccs as a component of Red Hat Enterprise Linux 10
- sgx-pccs-admin as a component of Red Hat Enterprise Linux 10
- sgx-pckid-tool as a component of Red Hat Enterprise Linux 10
- tdx-qgs as a component of Red Hat Enterprise Linux 10
- linux-sgx.src as a component of Red Hat Enterprise Linux 9
- nodejs-docs (nodejs:22) as a component of Red Hat Enterprise Linux 9
- nodejs-full-i18n (nodejs:22) as a component of Red Hat Enterprise Linux 9
- nodejs-libs (nodejs:22) as a component of Red Hat Enterprise Linux 9
- nodejs.src (nodejs:22) as a component of Red Hat Enterprise Linux 9
- nodejs (nodejs:22) as a component of Red Hat Enterprise Linux 9
- and 12 more
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Official vendor articles1 stored document
Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.
- morgan vulnerable to Log Forging via unescaped Unicode line separators · Advisory · expressjs/morgan · GitHub →Original publisher ↗Searchable text snapshot · Captured 27 Sep 2026expressjs / morgan Public Uh oh! There was an error while loading. Please reload this page . Notifications You must be signed in to change notification settings Fork 570 Star 8.2k Code Issues 12 Pull requests 7 Actions Security and quality 3 Insights Additional navigation options Code Issues Pull reques
04
Evidence and provenance
Published 28 Aug 2026 · Last source change 28 Aug 2026, 18:23 UTC · CWE-117 · Improper Output Neutralization for Logs
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-29
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-67720
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-15603 to remediation: access.redhat.com/CVE-2026-15603.Red Hat Product Security ↗
- Before
- remediation: access.redhat.com/CVE-2026-15603
- After
- remediation: access.redhat.com/CVE-2026-15603
- Remediation statusRemediation status changed from Awaiting fix to Mitigation available.Red Hat Product Security ↗
- Before
- Awaiting fix
- After
- Mitigation available
- ENISA EUVD mappingEUVD-2026-67720 was added to the official ENISA EUVD mapping for this CVE.ENISA EUVD ↗
- Before
- not recorded
- After
- {"euvdId":"EUVD-2026-67720"}
- Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: github.com/GHSA-jxfw-x594-9x9m.github.com ↗
- Before
- no authoritative guidance recorded
- After
- vendor advisory: github.com/GHSA-jxfw-x594-9x9m
- Catalogue recordCVE added to the BlackTree catalogue.CNA ↗
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.