CVE-2026-87859 morgan CVE debrief

Who should care

Node.js developers and administrators using the morgan middleware should assess their exposure and upgrade to morgan 1.12.1 or later to prevent log tampering and ensure accurate logging. The vulnerability can be used to forge log values, potentially leading to incorrect incident response. Affected operator, platform, vulnerability-management, and security-team impact should be reviewed to ensure proper mitigation.

Why it matters

The CVE-2026-87859 vulnerability in morgan HTTP request logger middleware for Node.js allows an unauthenticated remote attacker to inject malicious data into log files, potentially leading to log tampering and security issues. Node.js developers and administrators should assess their exposure and upgrade to morgan 1.12.1 or later.

• Log tampering can lead to inaccurate logging and potential security issues.
• An attacker can inject malicious data into log files, potentially leading to incorrect security assessments.
• The vulnerability can be used to forge log values, potentially leading to incorrect incident response.

Technical summary

The morgan HTTP request logger middleware for Node.js is vulnerable to log tampering due to a lack of double quote escaping in the escapeLogField() function. This allows an unauthenticated remote attacker to inject malicious data into log files, potentially leading to log tampering and security issues. The vulnerability can be used to forge log values, potentially leading to incorrect incident response. Node.js developers and administrators should assess their exposure and upgrade to morgan 1.12.1 or later to prevent log tampering.

Defensive priority

Upgrade to morgan 1.12.1 or later to prevent log tampering.

Recommended defensive actions

• Upgrade to morgan 1.12.1 or later
• Review and update logging configurations
• Monitor log files for potential tampering
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but the scope of affected systems and potential impact require further verification and defensive review. Affected product deployments need to be confirmed in managed environments, and owners should be assigned for follow-up. The official advisory or CVE record should be reviewed to validate affected scope, severity, and vendor guidance. Compensating controls for exposed systems should be reviewed while remediation is scheduled and verified.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.