NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

CVE-2026-28368 — undertow-core

HIGHFix: undertow-io/undertow@3ece0bf

CVE-2026-28368 is a high-severity (CVSS 8.7) CWE-444 vulnerability in io.undertow:undertow-core. A fix is available for io.undertow:undertow-core — see the affected versions and patch details below.

Undertow is Vulnerable to HTTP Request/Response Smuggling

Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-28368.

EPSS Exploitation Probability

via FIRST.org ↗
0.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs55th percentile — riskier than 55% of all scored CVEsHighest risk
0.00%0.46%0.92%1.39%0.0%0.7%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
☕io.undertow:undertow-core☕io.undertow:undertow-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenio.undertow:undertow-coreall versions2.2.40.Finalio.undertow:undertow-core:2.2.40.Final
☕Mavenio.undertow:undertow-core≥ 2.3.0.Final&&< 2.3.25.Final2.3.25.Finalio.undertow:undertow-core:2.3.25.Final

Affected Products

10 products · 11 configurations
Application
build of apache camel - hawtioredhat
1 version
4.0
Application
build of apache camel for spring bootredhat
1 version
4.0
Application
data gridredhat
1 version
8.0
OS
enterprise linuxredhat
1 version
9.0
Application
fuseredhat
1 version
7.0.0
Application
jboss enterprise application platformredhat
2 versions
7.0.08.0.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.undertow:undertow-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update io.undertow:undertow-core to 2.2.40.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-28368 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This flaw in Undertow's header parsing logic allows for request smuggling attacks when Undertow is deployed behind an upstream proxy. Crafted requests can bypass security controls by being interpreted differently by Undertow and the proxy, potentially leading to unauthorized access or cache poisoning.

Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Source: Red Hat security advisory for CVE-2026-28368 (CC BY 4.0)
ProductFixed inAdvisory
Red Hat JBoss Enterprise Application Platform 8.1.6io.undertow/undertow-core:2.3.24.SP2-redhat-00001RHSA-2026:25126
Red Hat JBoss Enterprise Application Platform 8.1 for RHEL 8eap8-activemq-artemis-0:2.40.0-7.redhat_00015.1.el8eapRHSA-2026:25125

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2026-28368 in your dependencies?

Find it across Maven, including transitive dependencies.

CVE-2026-28368: undertow-core — Fixed in 2.2.40.Final