Cleartext Transmission of Sensitive Information Affecting kibana-9.4 package, versions <9.4.2-r3


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.12% (3rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-KIBANA94-17328210
  • published13 Jun 2026
  • disclosed17 Jul 2026

Introduced: 13 Jun 2026

CVE-2026-48022  (opens in a new tab)
CWE-319  (opens in a new tab)
CWE-346  (opens in a new tab)
CWE-522  (opens in a new tab)

How to fix?

Upgrade Chainguard kibana-9.4 to version 9.4.2-r3 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kibana-9.4 package and not the kibana-9.4 package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

@hapi/wreck is an HTTP client utility. Prior to 18.1.2, Wreck strips credential headers including Authorization, Cookie, and Proxy-Authorization before following a cross-origin redirect, but the origin check compares hostnames only and ignores scheme and port, so credentials are forwarded intact across same-host port changes and HTTPS-to-HTTP downgrades, allowing a co-tenant on an adjacent port or a network-position attacker capable of forging a redirect to capture bearer tokens, session cookies, and proxy credentials and impersonate the victim against the upstream service. This issue is fixed in version 18.1.2.