CVE-2026-40542
Authentication Bypass in Apache HttpClient 5.6 via SCRAM-SHA
Publication date: 2026-04-22
Last updated on: 2026-05-01
Assigner: Apache Software Foundation
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| apache | httpclient | 5.6 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-304 | The product implements an authentication technique, but it skips a step that weakens the technique. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify how the vulnerability in Apache HttpClient 5.6 impacts compliance with common standards and regulations such as GDPR or HIPAA.
Can you explain this vulnerability to me?
This vulnerability is a missing critical step in the authentication process in Apache HttpClient version 5.6. It allows an attacker to cause the client to accept SCRAM-SHA-256 authentication without proper mutual authentication verification.
This means that the client may trust an authentication attempt that has not been fully verified, potentially allowing unauthorized access.
Users are recommended to upgrade to version 5.6.1, which fixes this issue.
How can this vulnerability impact me? :
This vulnerability can impact you by allowing an attacker to bypass proper mutual authentication verification when using Apache HttpClient 5.6 with SCRAM-SHA-256 authentication.
As a result, an attacker could potentially impersonate a legitimate server or client, leading to unauthorized access or data interception.
What immediate steps should I take to mitigate this vulnerability?
Users are recommended to upgrade Apache HttpClient to version 5.6.1, which fixes the authentication issue allowing acceptance of SCRAM-SHA-256 without proper mutual authentication verification.