CVE-2026-48856

httpc leaks Authorization header to cross-origin redirect targets

MEDIUM
6.5
CVSS Score
Published: June 10, 2026 at 02:41 PM UTC
Updated: October 26, 2026 at 11:10 AM UTC
2 products affected across 1 vendorErlang /otpErlang /inets

Using OTP by Erlang?

Get instant alerts when new vulnerabilities affect OTP - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.5
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

Description

Sensitive Data Exposure vulnerability in Erlang OTP inets (httpc_response module) allows Retrieve Embedded Sensitive Data. The httpc client forwards the Authorization and Proxy-Authorization request headers to redirect targets without checking whether the redirect crosses an origin boundary. httpc_response:redirect/2 constructs the redirected request by updating only the host field of the header record; all other fields (including authorization and proxy_authorization) are copied verbatim. The redirect target host is never compared against the original host. autoredirect defaults to true, so this affects all httpc callers that do not explicitly disable automatic redirects. An attacker who controls a server that the victim contacts via httpc can issue a cross-origin 3xx redirect to a server they also control. The Authorization header (including Basic credentials derived from URL userinfo via httpc_request:handle_user_info/2) is forwarded to the redirect target, allowing credential theft. The same applies to the Proxy-Authorization header. This vulnerability is associated with program files lib/inets/src/http_client/httpc_response.erl. This issue affects OTP from 17.0 before 29.0.2, 28.5.0.2 and 27.3.4.13 corresponding to inets from 5.10 before 9.7.1, 9.6.2.2 and 9.3.2.6.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.10 ≤ v < 9.3.2.69.6 ≤ v < 9.6.2.29.7 ≤ v < 9.7.1
Affected range stops below 9.3.2.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.6.2.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.7.1, so it looks safe — our inference, not a vendor statement
17.0 ≤ v < 27.3.4.1328.0 ≤ v < 28.5.0.229.0 ≤ v < 29.0.217.05.1084adefa331c4159d432d22840663c38f155cd4c1
Affected range stops below 27.3.4.13, so it looks safe — our inference, not a vendor statement
Affected range stops below 28.5.0.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 29.0.2, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 688d748d6f7a6a06b13b662a1d3de8af97079612 (unaffected)
Vendor states this is fixed in f78fae9294886f95545a2212671282eda230def1 (unaffected)

References (6)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-601

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card