CVE-2025-12543: Undertow-core: undertow http server fails to reject malformed host headers leading to potential cache poisoning and ssrf

Published Oct 31, 2025
·
Updated

A flaw was found in the Undertow HTTP server core, which is used in WildFly, JBoss EAP, and other Java applications. The Undertow library fails to properly validate the Host header in incoming HTTP requests. As a result, requests containing malformed or malicious Host headers are processed without rejection, enabling attackers to poison caches, perform internal network scans, or hijack user sessions.

Other sources

A flaw was found in the Undertow HTTP server core, which is used in WildFly, JBoss EAP, and other Java applications. The Undertow library fails to properly validate the Host header in incoming HTTP requests.As a result, requests containing malformed or malicious Host headers are processed without rejection, enabling attackers to poison caches, perform internal network scans, or hijack user sessions.

NVD

An Improper Input Validation vulnerability exists in the Undertow HTTP server (io.undertow:undertow-core) where the implementation does not return a 400 Bad Request response when receiving requests with invalid or malformed Host headers. The flaw can be exploited by remote attackers via specially crafted HTTP requests. Depending on the deployment, the issue enables web cache poisoning, session hijacking, or server-side request forgery (SSRF). Attackers may inject malicious responses into caches, steal authentication tokens, or redirect users to malicious endpoints. Successful exploitation can result in complete account takeover, widespread credential theft, or unauthorized access to internal network resources, thereby compromising confidentiality and integrity of user data.

Red Hat

Apache Commons Codec could allow a remote attacker to obtain sensitive information, caused by the improper validation of input. An attacker could exploit this vulnerability using a method call to obtain sensitive information.

IBM

Affected Software

15 affected components
maven/io.undertow/undertow-core
maven/io.undertow:undertow-core<=2.4.0.Alpha1
redhat Build Of Apache Camel Spring Boot<4.14.4
redhat Data Grid=8.0
redhat Fuse=7.0.0
redhat JBoss Enterprise Application Platform>=8.0<8.0.12
redhat JBoss Enterprise Application Platform>=8.1.0<8.1.3
redhat JBoss Enterprise Application Platform
redhat JBoss Enterprise Application Platform=7.0.0
redhat Jboss Enterprise Application Platform Expansion Pack
redhat Process Automation=7.0
redhat Single Sign-on=7.0
redhat undertow<2.2.39
redhat undertow>=2.3.0<2.3.21
IBM watsonx.data intelligence<=5.2.0, 5.2.1, 5.3.0, 5.3.1

Event History

Oct 31, 2025
Data Sourced
via Red Hat·06:53 AM
DescriptionSeverityAffected Software
Jan 7, 2026
CVE Published
via MITRE·04:04 PM
Data Sourced
via MITRE·04:04 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:15 PM
Affected Software
Advisory Published
via GitHub·06:30 PM
Data Sourced
via GitHub·06:30 PM
DescriptionSeverityWeaknessAffected Software
Apr 27, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-12543?

CVE-2025-12543 is classified as a critical vulnerability due to its potential to allow attackers to execute HTTP request smuggling attacks.

2

How do I fix CVE-2025-12543?

To fix CVE-2025-12543, update the Undertow library to the latest patched version provided by Red Hat.

3

Which software is affected by CVE-2025-12543?

CVE-2025-12543 affects the Undertow HTTP server core, particularly in environments using WildFly and JBoss EAP.

4

What are the risks associated with CVE-2025-12543?

The risks include potential exploitation through crafted HTTP requests, leading to security breaches and unauthorized access to applications.

5

Is there a workaround for CVE-2025-12543?

While updating is recommended, temporarily restricting incoming HTTP requests to valid Host headers can serve as a workaround until a patch is applied.

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