dbcve.org
Build Of Apache CamelWeb server / proxy · Redhat

CVE-2025-12543

CRITICAL · 9.6 CVSS v3.1 Developing Published 2026-01-07
Fix available
A fix is available. Upgrade to 2.2.39 / 2.3.21 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 5mo ago

Surfaced from public web coverage — external links open in a new tab.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-08-11.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Build Of Apache CamelWeb server / proxy
Affected:< 4.14.4
Data GridApplication
Affected:= 8.0
FuseApplication
Affected:= 7.0.0
Jboss Enterprise Application PlatformApplication
Affected:>= 8.0, < 8.0.12>= 8.1.0, < 8.1.3all versions= 7.0.0
Jboss Enterprise Application Platform Expansion PackApplication
Affected:all versions
Process AutomationApplication
Affected:= 7.0
Single Sign OnApplication
Affected:= 7.0
UndertowApplication
Affected:< 2.2.39>= 2.3.0, < 2.3.21

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.2.39 / 2.3.21 / 4.14.4 or later
Fixed in 2.2.392.3.214.14.4
Recommended fix High confidence

Undertow 2.2.39+/2.3.21+; JBoss EAP 8.0.12+; JBoss EAP 8.1.3+; Camel 4.14.4+ (or apply Red Hat security advisories for Fuse, Data Grid, Process Automation, SSO)

  1. Identify the specific affected component in your deployment (Undertow, JBoss EAP, Fuse, Camel, Data Grid, Process Automation, or SSO)
  2. For Undertow direct deployments: upgrade Undertow to version 2.2.39 or later (2.x series) or 2.3.21 or later (2.3.x series)
  3. For JBoss EAP 8.0: upgrade to version 8.0.12 or later
  4. For JBoss EAP 8.1: upgrade to version 8.1.3 or later
  5. For JBoss EAP 7.0: contact Red Hat for available patches as the description indicates all versions are affected
  6. For Apache Camel: upgrade to version 4.14.4 or later
  7. For Fuse, Data Grid, Process Automation, and SSO: apply the corresponding Red Hat security update that patches the Undertow component
  8. After upgrade, verify that the Host header validation is working correctly by testing with malformed headers
Caveat Review release notes for each product version; minor version upgrades typically have low risk but validate application compatibility

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12543 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-12543 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data