CVE-2025-7339 | on-headers vulnerable to http response header manipulation

on-headers is a node.js middleware for listening to when a response writes headers. A bug in on-headers versions `<1.1.0` may result in response headers being inadvertently modified when an array is passed to `response.writeHead()`. Users should upgrade to version 1.1.0 to receive a patch. Uses are strongly encouraged to upgrade to `1.1.0`, but this issue can be worked around by passing an object to `response.writeHead()` rather than an array.

Published: 2025-07-17 Last update: 2026-04-15 Assigner: ce714d77-add3-4f53-aff5-83d477b104bb Source: ce714d77-add3-4f53-aff5-83d477b104bb
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-7339 is rated Low Risk (14/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.01%). Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-7339

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-07-18 — 0.01% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-7339

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.4 3.1 LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 0.8 2.5 ce714d77-add3-4f53-aff5-83d477b104bb

Weakness enumeration for CVE-2025-7339

GitHub Security Advisory for CVE-2025-7339

GHSA-76c9-3jph-rj3q · Severity: low · Ecosystem: npm — on-headers is vulnerable to http response header manipulation

OS Trackers for CVE-2025-7339

vendor priority summary link
debian not yet assigned CVE-2025-7339 not yet assigned priority: Debian including 1 source packages (node-on-headers), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 3, open 2. https://security-tracker.debian.org/tracker/CVE-2025-7339
redhat low — https://access.redhat.com/security/cve/CVE-2025-7339
suse medium CVE-2025-7339 severity moderate: SUSE including 34 source package names (corepack20, corepack22, …), 199 product×package rows across 26 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS, … (26 product lines)): Known Not Affected 199. https://www.suse.com/security/cve/CVE-2025-7339/
ubuntu medium CVE-2025-7339 medium priority: Ubuntu including 1 source packages (node-on-headers), 8 status rows across 8 suites (bionic, focal, jammy, noble, plucky, questing, upstream, xenial): needs-triage 6, ignored 1, released 1. https://ubuntu.com/security/CVE-2025-7339

Affected software / configurations for CVE-2025-7339

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-7339

cvelogic Threat Intelligence