All vulnerabilities

npm

CVE-2026-71849

Hono: Proxy Helper does not remove response headers listed in the `Connection` header

Severity
Low 3.7
Published
7 Aug 2026
Last changed
10 Sept 2026
Added to UpHeron
22 Oct 2026
Fixed in
4.12.34
Exploit chance
0.4% in the next 30 daysHigher than 29% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Information exposure (CWE-200)
Attack
Over the network · Only under certain conditions · No login needed · No user action needed
Attacker can
Read some data
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
Also known as
GHSA-79qm-7rj5-m7r9
Sources
OSV.dev and GitHub

Description

The Proxy Helper (hono/proxy) does not remove response headers named by the origin's Connection header. Headers that the origin marked as connection-scoped are therefore forwarded to clients.

Per RFC 9110 Section 7.6.1, an intermediary must remove the header fields listed in a message's Connection header field before forwarding the message, in addition to the well-known hop-by-hop headers. The proxy() function removed the well-known hop-by-hop headers (including Connection itself) from origin responses, but did not remove the headers that the response's Connection header field designated as connection-scoped.

This issue arises when an application proxies responses from an origin that declares additional, non-standard headers as hop-by-hop via the Connection response header.

A client may receive response headers that the origin intended only for its immediate peer. This may lead to:

  • Disclosure of connection-scoped or internal metadata contained in such headers
From the GitHub Advisory Database, CC BY 4.0. Shortened; the full text is there.

Affected software

SoftwareAffected versions
hononpm · osv:npm:hono
  • From 4.7.0 before 4.12.34

About hono

Weekly downloads (npm)
108,805,821npm, 16 Nov 2026

References