Apache HttpClient accepts SCRAM-SHA-256 authentication without proper mutual authentication verification
Published 22 Apr 2026 · Updated 10 Sept 2026
Is your project on an affected org.apache.httpcomponents.client5:httpclient5?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- >=5.6-alpha1 <5.6.1
- Fixed in
- 5.6.1
mvn versions:use-dep-version -Dincludes=org.apache.httpcomponents.client5:httpclient5 -DdepVersion=5.6.1 -DforceVersion=trueDetails
Missing critical step in authentication in Apache HttpClient 5.6 allows an attacker to cause the client to accept SCRAM-SHA-256 authentication without proper mutual authentication verification. Users are recommended to upgrade to version 5.6.1, which fixes this issue.
Is GHSA-v468-qcjx-r72w in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.apache.httpcomponents.client5:httpclient5, and gives you the command that fixes it.
More advisories for org.apache.httpcomponents.client5:httpclient5
- MediumCVE-2026-64607Apache HttpComponents Client: Connection Leak on Content-Encoding Decode Error Leads to Pool Exhaustion DoS · 31 Jul 2026
- HighCVE-2025-27820Apache HttpClient disables domain checks · 24 Apr 2025
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.