Description
Hono is a Web application framework that provides support for any JavaScript runtime. From 4.7.0 to 4.12.33, the Proxy Helper proxy() function in hono/proxy does not remove response headers named by the origin's Connection header. 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, but the proxy() function only removed the well known hop by hop headers, including Connection itself, from origin responses. A client may therefore receive response headers that the origin intended only for its immediate peer, disclosing connection scoped or internal metadata contained in such headers, when an application proxies responses from an origin that declares additional, non standard headers as hop by hop via the Connection response header. This issue is fixed in version 4.12.34.
Published: 2026-08-07
Score: 3.7 Low
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

An application using Hono’s proxy helper may leak internal or connection‑specific metadata to clients. The proxy() function fails to remove headers listed in the origin’s Connection header, so hop‑by‑hop headers that are not part of the standard set can be forwarded to the client, exposing data that was intended only for the immediate peer. This behavior falls under CWE‑200, the general class of information‑disclosure weaknesses.

Affected Systems

The vulnerability affects the Hono web application framework from version 4.7.0 up through 4.12.33. The fix was introduced in release 4.12.34.

Risk and Exploitability

The CVSS score is 3.7, indicating a low severity impact, and no EPSS score is available; the vulnerability is not listed in CISA’s KEV. An attacker can trigger the leak by directing a client request that is proxied by an application leveraging the flawed proxy helper. The attack requires no authentication or privileged access beyond the ability to use the application’s proxy feature, and the exposed headers can reveal sensitive connection information. While the potential for serious damage is limited, the information leakage could be valuable to an adversary conducting reconnaissance on the deployment.

Generated by OpenCVE AI on August 7, 2026 at 20:39 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Hono to version 4.12.34 or newer, where the proxy helper now removes all headers specified in the Connection response header.
  • If an upgrade is not immediately possible, modify or extend the proxy helper code to strip every header name listed in the Connection header from the response before it is forwarded to the client.
  • As a last resort, configure the application or an upstream reverse proxy so that responses containing custom Connection header values are not proxied, thereby preventing inadvertent disclosure of hop‑by‑hop metadata.

Generated by OpenCVE AI on August 7, 2026 at 20:39 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-79qm-7rj5-m7r9 Hono: Proxy Helper does not remove response headers listed in the `Connection` header
History

Fri, 07 Aug 2026 19:00:00 +0000

Type Values Removed Values Added
Description Hono is a Web application framework that provides support for any JavaScript runtime. From 4.7.0 to 4.12.33, the Proxy Helper proxy() function in hono/proxy does not remove response headers named by the origin's Connection header. 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, but the proxy() function only removed the well known hop by hop headers, including Connection itself, from origin responses. A client may therefore receive response headers that the origin intended only for its immediate peer, disclosing connection scoped or internal metadata contained in such headers, when an application proxies responses from an origin that declares additional, non standard headers as hop by hop via the Connection response header. This issue is fixed in version 4.12.34.
Title Hono: Proxy Helper does not remove response headers listed in the `Connection` header
Weaknesses CWE-200
References
Metrics cvssV3_1

{'score': 3.7, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-08-07T18:38:16.287Z

Reserved: 2026-08-07T18:26:53.523Z

Link: CVE-2026-71849

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-07T20:45:03Z

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor