---
title: "GHSA-76c9-3jph-rj3q: on-headers is vulnerable to http response header manipulation"
description: "Low severity. on-headers is vulnerable to http response header manipulation. Affects on-headers; fixed in 1.1.0."
url: https://inlinr.com/advisories/GHSA-76c9-3jph-rj3q
lang: en
---

[Packages](https://inlinr.com/packages) / [on-headers](https://inlinr.com/packages/on-headers) / [Security](https://inlinr.com/packages/on-headers/security)

Low Vulnerability GHSA-76c9-3jph-rj3q CVE-2025-7339 Published 17 Jul 2025

# on-headers is vulnerable to http response header manipulation

Your version 

Affected releases · [on-headers](https://inlinr.com/packages/on-headers)

- 1.x 1.0.0 – 1.0.2 Fixed in 1.1.0
- 0.0.x 0.0.0 No fix on this line yet

On 1.x, the newest line:

```
npm install on-headers@1.1.0
```

Every release on a timeline

1.x 

1. Affected

1.0.0 – 1.0.2  
3 releases
2. Fixed

1.1.0  
1 release, latest

0.x 

1. Affected

0.0.0  
1 release

5 stable releases of on-headers, oldest to newest, one row per major.

## What happens

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.

## How it is exploited

Exploitable with local access, with an admin account and no action from a user.

- **Confidentiality**: low
- **Integrity**: low
- **Availability**: none

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

## References

- [Reference](https://github.com/jshttp/on-headers/security/advisories/GHSA-76c9-3jph-rj3q "https://github.com/jshttp/on-headers/security/advisories/GHSA-76c9-3jph-rj3q")  
github.com/jshttp/on-headers/security/advisorie…
- [NVD](https://nvd.nist.gov/vuln/detail/CVE-2025-7339 "https://nvd.nist.gov/vuln/detail/CVE-2025-7339")  
nvd.nist.gov/vuln/detail/CVE-2025-7339
- [Issue](https://github.com/expressjs/morgan/issues/315 "https://github.com/expressjs/morgan/issues/315")  
#315
- [Issue](https://github.com/jshttp/on-headers/issues/15 "https://github.com/jshttp/on-headers/issues/15")  
#15
- [Fix commit](https://github.com/jshttp/on-headers/commit/c6e384908c9c6127d18831d16ab0bd96e1231867 "https://github.com/jshttp/on-headers/commit/c6e384908c9c6127d18831d16ab0bd96e1231867")  
c6e3849
- [Reference](https://cna.openjsf.org/security-advisories.html "https://cna.openjsf.org/security-advisories.html")  
cna.openjsf.org/security-advisories.html
- [Package](https://github.com/jshttp/on-headers "https://github.com/jshttp/on-headers")  
github.com/jshttp/on-headers

A whole project to check? Paste its package.json in the [dependency check](https://inlinr.com/tools/dependency-check): every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.
