CVE-2026-28369: Red Hat JBoss Enterprise Application Platform 8.1.6 jboss-eap · HTTP Request/Response Smuggling
Affects Red Hat JBoss Enterprise Application Platform 8.1.6 jboss-eapSource CVE Database V5
Not known to be exploited · CVSS 8.7 High : upgrade the Red Hat redhat/jboss-eap package to 8.1.6 soon.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 8.1.6
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 27 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade the Red Hat redhat/jboss-eap package to 8.1.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Red Hatredhat/jboss-eappkg:rpm/redhat/jboss-eapOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Red Hat has released an official security update in Red Hat JBoss Enterprise Application Platform version 8.1.6 that addresses this vulnerability. Users should apply this update promptly. Before updating, ensure all previous errata are applied and back up existing installations, including applications, configurations, and databases. No other mitigations are specified by the vendor. Patch status is confirmed by Red Hat advisories RHSA-2026:25125 and RHSA-2026:25126.
Description
A flaw was found in Undertow. When Undertow receives an HTTP request where the first header line starts with one or more spaces, it incorrectly processes the request by stripping these leading spaces. This behavior, which violates HTTP standards, can be exploited by a remote attacker to perform request smuggling. Request smuggling allows an attacker to bypass security mechanisms, access restricted information, or manipulate web caches, potentially leading to unauthorized actions or data exposure.