dbcve.org
Build Of Apache Camel HawtioWeb server / proxy · Redhat

CVE-2026-28368

CRITICAL · 9.1 CVSS v3.1 Published 2026-03-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 Undertow. This vulnerability allows a remote attacker to construct specially crafted requests where header names are parsed differently by Undertow compared to upstream proxies. This discrepancy in header interpretation can be exploited to launch request smuggling attacks, potentially bypassing security controls and accessing unauthorized resources.

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 · moderate confidence

This is an HTTP request smuggling vulnerability in Undertow, a Java-based web server. Attackers can exploit differences in header parsing between Undertow and upstream proxies by crafting malicious requests with specially formatted header names. This allows smuggling requests through security boundaries, bypassing controls like WAFs and load balancers to access unauthorized backend resources.

MitigationUpgrade Undertow to the patched version or apply configuration changes to normalize header parsing between Undertow and any upstream proxies/load balancers. Implement strict header validation and enable any available HTTP parsing security options.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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 Camel HawtioWeb server / proxy
Affected:= 4.0
Build Of Apache Camel For Spring BootWeb server / proxy
Affected:= 4.0
Data GridApplication
Affected:= 8.0
FuseApplication
Affected:= 7.0.0
Jboss Enterprise Application PlatformApplication
Affected:= 7.0.0= 8.0.0
Jboss Enterprise Application Platform Expansion PackApplication
Affected:all versions
Process AutomationApplication
Affected:= 7.0
Single Sign OnApplication
Affected:= 7.0

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Red Hat product and version
    Check the version of the Red Hat product installed (e.g., JBoss EAP, Fuse, Data Grid, Camel, SSO, Process Automation) using the product-specific version command or check the installed packages. Compare against the affected versions: JBoss EAP 7.0.0 or 8.0.0, Fuse 7.0.0, Data Grid 8.0, Camel/Hawtio 4.0, SSO 7.0, Process Automation 7.0, or EAP Expansion Pack (all versions).
    Affected if The installed product version matches one of the affected versions listed.
  2. Confirm Undertow is being used as the embedded web server
    Check for the presence of Undertow in the deployment. This can be done by searching for undertow-core jar files in the application lib directory, or checking the product's dependencies/configuration that specify Undertow as the web server (common in JBoss EAP and Fuse).
    Affected if Undertow is embedded and handling HTTP requests.
  3. Verify presence of a reverse proxy or load balancer in front of Undertow
    Examine the network architecture and configuration to determine if a reverse proxy (such as Apache HTTP Server, Nginx, HAProxy) or load balancer sits in front of the Undertow server handling incoming HTTP traffic.
    Affected if A reverse proxy or load balancer is forwarding requests to Undertow.
  4. Check for inconsistent Content-Length or Transfer-Encoding header handling
    Analyze the Undertow configuration and any proxy configurations for differences in how HTTP request boundaries (Content-Length, Transfer-Encoding headers) are parsed and validated. Compare the proxy configuration with Undertow's expected behavior.
    Affected if The upstream proxy parses HTTP headers differently from Undertow, creating a potential smuggling vector.
  5. Review HTTP header parsing behavior in test environment
    If possible, send crafted HTTP requests with ambiguous header configurations (e.g., duplicate Content-Length headers, conflicting Transfer-Encoding and Content-Length) to observe how Undertow interprets them versus how the upstream proxy interprets them.
    Affected if Undertow and the upstream proxy interpret the same request differently, indicating the vulnerability is present.

You are affected if you are running any of the listed Red Hat products at the specified versions with Undertow behind a reverse proxy or load balancer that parses HTTP headers inconsistently with Undertow.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Undertow to the patched version or apply configuration changes to normalize header parsing between Undertow and any upstream proxies/load balancers. Implement strict header validation and enable any available HTTP parsing security options.

Fix this in Build Of Apache Camel Hawtio Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28368 — 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-2026-28368 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