CVE-2026-40542: Apache HttpClient: SCRAM-SHA-256 mutual authentication bypass may cause the client to accept authentication without proper mutual authentication verification

Published Apr 22, 2026
·
Updated

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.

Affected Software

2 affected components
Apache HttpClient=5.6
Apache HttpClient=5.6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Apache HttpClient to a version that resolves this vulnerability.

    Fixed in 5.6.1Patch CVE-2026-40542

Event History

Apr 22, 2026
CVE Published
via MITRE·07:07 AM
Data Sourced
via MITRE·07:07 AM
DescriptionWeakness
Data Sourced
via Red Hat·08:01 AM
DescriptionSeverityAffected Software
Data Sourced
via NVD·08:16 AM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-40542?

CVE-2026-40542 has been assigned a high severity rating due to its potential to allow unauthorized access through mutual authentication bypass.

2

How do I fix CVE-2026-40542?

To fix CVE-2026-40542, upgrade Apache HttpClient to version 5.7 or later where this vulnerability is addressed.

3

Who is affected by CVE-2026-40542?

CVE-2026-40542 affects users of Apache HttpClient version 5.6 when utilizing SCRAM-SHA-256 authentication.

4

What is the impact of CVE-2026-40542?

The impact of CVE-2026-40542 is that it can lead to unauthorized access as the client fails to properly verify mutual authentication.

5

When was CVE-2026-40542 published?

CVE-2026-40542 was published in April 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203