---
title: "on-headers security advisories"
description: "1 known security advisory for on-headers, with the versions they affect and the version that fixes each."
url: https://inlinr.com/packages/on-headers/security
lang: en
---

[Packages](https://inlinr.com/packages)

# on-headers

1.1.0 · 17 Jul 2025 MIT 71.2M / week [Repository](https://github.com/jshttp/on-headers) [Homepage](https://github.com/jshttp/on-headers#readme) [npm](https://www.npmjs.com/package/on-headers) [Atom feed](https://inlinr.com/packages/feed/on-headers)

Your version 

## Security advisories

From OSV, open ones first. Each release line gets its own fix: an older major is fixed by a patch on that major, not by moving to the newest one.

| Line | Newest | Where it stands                                                        |
| ---- | ------ | ---------------------------------------------------------------------- |
|      | 1.1.0  | Safe from 1.1.0                                                        |
|      | 0.0.0  | 1 open advisory, worst low  · last release May 2014, no longer updated |

- Low  
[on-headers is vulnerable to http response header manipulation](https://inlinr.com/advisories/GHSA-76c9-3jph-rj3q)GHSA-76c9-3jph-rj3q · 17 Jul 2025  
fixed in 1.1.0

### Quality and security signals

What [npm](https://www.npmjs.com/package/on-headers) and [deps.dev](https://deps.dev/npm/on-headers) say about the latest release. Signals, not a verdict.

Reading npm and deps.dev…

Reading releases, release notes and advisories…

Registry facts last checked 21 Nov 2026\. Releases and advisories last read 21 Nov 2026.

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.
