Most recent entries from all

CLEANSTART-2026-AV60851 — Security fix for CVE-2026-71849 applied in: langfuse 3.208.0-r1, langfuse 3.213.0-r1, langfuse 4.10.0-r1, langfuse 4.12…

Affected: CleanStart: langfuse, CleanStart: langfuse-worker, CleanStart: n8n

CVE-2026-71849 affects multiple packages. This issue is resolved in later releases. See references for individual vulnerability details.

EUVD-2026-349691

fkie_cve-2026-71849

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.

GHSA-79qm-7rj5-m7r9 — Hono: Proxy Helper does not remove response headers listed in the `Connection` header

Affected: npm: hono

### Summary

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.

### Details

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.

### Impact

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

This issue affects applications that use the Proxy Helper (`hono/proxy`) to forward responses from origins that list custom header names in their `Connection` response header. Applications whose origins only use the standard hop-by-hop headers are not affected.

WID-SEC-W-2026-3221 — IBM App Connect Enterprise: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM App Connect Enterprise ausnutzen, um beliebigen Programmcode auszuführen, erweiterte Berechtigungen zu erlangen, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen oder Denial-of-Service-Zustände herbeizuführen.