Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

on-headers vulnerable to http response header manipulation

CVSS 3.1 3.4 LOWEUVD CVSS 3.1 3.4 CVSS 3.1 · ce714d77-add3-4f53-aff5-83d477b104bb · Secondary 3.4 LOWCVSS_V3 Publisher rating LOWFixed by on-headers 1.1.0KEV status unknown

cve-program · CVE-2025-7339

Published

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.

Read the publisher's advisory

euvd · EUVD-2025-21784

Published

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.

Read the publisher's advisory

nvd · CVE-2025-7339

Published

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.

Read the publisher's advisory

osv · GHSA-76c9-3jph-rj3q

Published

### Impact 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()` ### Patches Users should upgrade to `1.1.0` ### Workarounds Uses are 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.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2025-7339

Published

on-headers

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "defaultStatus": "unaffected",
                    "product": "on-headers",
                    "vendor": "jshttp",
                    "versions": [
                        {
                            "lessThan": "1.1.0",
                            "status": "affected",
                            "version": "0",
                            "versionType": "semver"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2025-21784

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Jul 17, 2025, 3:47:39 PM

dateUpdated: Jul 17, 2025, 8:24:47 PM

7 related source bulletins · separate from aliases

WID-SEC-W-2025-1929: IBM App Connect Enterprise: Mehrere Schwachstellen

CVE-2025-7338 · CVE-2025-7339 · CVE-2025-7783

RHSA-2025:21704: Red Hat Security Advisory: Red Hat OpenShift Data Foundation 4.20 security, enhancement & bug fix update

CVE-2022-0155 · CVE-2022-0536 · CVE-2024-45338 · CVE-2025-5889 · CVE-2025-7339 · CVE-2025-7783 · CVE-2025-22869

openSUSE-SU-2026:20919-1: Security update for agama-web-ui

CVE-2025-7339 · CVE-2026-42041 · CVE-2026-42264 · CVE-2026-9277

msrc_CVE-2025-7339: on-headers vulnerable to http response header manipulation

CVE-2025-7339

WID-SEC-W-2025-2360: Oracle Communications Applications: Mehrere Schwachstellen

CVE-2024-12133 · CVE-2024-28182 · CVE-2024-35164 · CVE-2024-37371 · CVE-2024-50609 · CVE-2024-51504 · CVE-2024-57699 · CVE-2024-7254 · CVE-2024-8006 · CVE-2025-27210 · CVE-2025-27533 · CVE-2025-27553 · CVE-2025-27817 · CVE-2025-32415 · CVE-2025-32990 · CVE-2025-4517 · CVE-2025-48734 · CVE-2025-48924 · CVE-2025-48976 · CVE-2025-48989 · CVE-2025-49796 · CVE-2025-5115 · CVE-2025-52999 · CVE-2025-5318 · CVE-2025-53864 · CVE-2025-5399 · CVE-2025-54090 · CVE-2025-55163 · CVE-2025-5889 · CVE-2025-59375 · CVE-2025-6965 · CVE-2025-7339 · CVE-2025-8058 · CVE-2025-9086

NCSC-2025-0330: Kwetsbaarheden verholpen in Oracle Communications producten

CVE-2023-26555 · CVE-2024-7254 · CVE-2024-8006 · CVE-2024-12133 · CVE-2024-28182 · CVE-2024-35164 · CVE-2024-37371 · CVE-2024-47554 · CVE-2024-50609 · CVE-2024-51504 · CVE-2024-57699 · CVE-2025-1948 · CVE-2025-3576 · CVE-2025-4373 · CVE-2025-4517 · CVE-2025-4802 · CVE-2025-5115 · CVE-2025-5318 · CVE-2025-5399 · CVE-2025-5889 · CVE-2025-6965 · CVE-2025-7339 · CVE-2025-7425 · CVE-2025-7962 · CVE-2025-8058 · CVE-2025-8916 · CVE-2025-9086 · CVE-2025-25724 · CVE-2025-27210 · CVE-2025-27533 · CVE-2025-27553 · CVE-2025-27587 · CVE-2025-27817 · CVE-2025-32415 · CVE-2025-32728 · CVE-2025-32990 · CVE-2025-48734 · CVE-2025-48924 · CVE-2025-48976 · CVE-2025-48989 · CVE-2025-49796 · CVE-2025-52999 · CVE-2025-53547 · CVE-2025-53643 · CVE-2025-53864 · CVE-2025-54090 · CVE-2025-55163 · CVE-2025-57803 · CVE-2025-58057 · CVE-2025-59375

WID-SEC-W-2025-2345: IBM DataPower Gateway: Schwachstelle ermöglicht Manipulation von Daten und potenziell Denial of Service

CVE-2025-7339

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2025-7339

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Deferred

Weakness classifications: CWE-241

Original publisher date fields

published: 2025-07-17T16:15:35.403

lastModified: 2026-06-17T10:04:45.180

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-76c9-3jph-rj3q

Published

on-headers

npm

SEMVER · introduced 0 → fixed 1.1.0

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 11:47 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current