libcurl can leak the password stored in a .netrc file when a request that uses that file is redirected to a different host. The leak occurs under certain circumstances that are not fully detailed in the advisory. Based on the description, it is inferred that these circumstances may involve the reuse of a single HTTP proxy connection for the original and the redirected request, thereby exposing the credentials to the second host. The flaw exposes sensitive authentication information and is classified as exposure of data and information disclosure (CWE‑200, CWE‑201).

The vulnerability affects the libcurl library in the curl project. Any application that links against libcurl and is configured to use a .netrc file for authentication while also following HTTP redirects is potentially at risk. No specific version numbers are supplied by the CNA, so all builds that support .netrc usage and do not isolate proxy connections before the fix should be considered at risk.

The CVSS score of 5.3 indicates a moderate severity. The EPSS score of <1 % suggests a very low probability of exploitation, and the vulnerability is not listed in CISA's KEV catalog. Based on the description and CVE details, it is inferred that the attacker would need to intercept or control the cleartext traffic sent through the HTTP proxy that the client reuses for the initial and redirected requests. Once the proxy traffic is observable, the leaked credentials can be captured, leading to credential theft. Because exploitation requires specific proxy conditions and a network position that sees both requests, it is inferred that the overall risk is moderate but routine remediation is recommended.