Credential disclosure via hostname-only redirect origin checks
Published Jul 17, 2026 · Updated Jul 17, 2026
Credential exposure in @hapi/wreck before 18.1.2 allows remote attackers to capture sensitive headers through crafted redirects. The redirect path in lib/index.js compares only URL hostnames, so same-host port or scheme changes retain Authorization, Cookie, and Proxy-Authorization headers. Redirect following must be enabled and an attacker must control the redirect target or network path; disclosure enables upstream impersonation.
Summary
What happened
Credential exposure in @hapi/wreck before 18.1.2 allows remote attackers to capture sensitive headers through crafted redirects. The redirect path in lib/index.js compares only URL hostnames, so same-host port or scheme changes retain Authorization, Cookie, and Proxy-Authorization headers. Redirect following must be enabled and an attacker must control the redirect target or network path; disclosure enables upstream impersonation.
The record
- CVE
- CVE-2026-48022
- Published
- Jul 17, 2026
- Updated
- Jul 17, 2026
- Vendor
- hapi
- Product
- @hapi/wreck
- Classifications
- CWE-319, CWE-522, CWE-940, CWE-346, CWE-200, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 17, 2026CVE publishedPublication date reported by the CVE source.
- Jul 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 18.1.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo