Bug 2480601 (CVE-2026-15554) - CVE-2026-15554 undertow-core: Undertow: Authentication Bypass via AJP ssl_cert/is_ssl Forgery
Summary: CVE-2026-15554 undertow-core: Undertow: Authentication Bypass via AJP ssl_cer...
Keywords:
Status: NEW
Alias: CVE-2026-15554
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-05-21 19:44 UTC by OSIDB Bzimport
Modified: 2026-08-11 17:42 UTC (History)
21 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:53644 0 None None None 2026-08-11 16:37:31 UTC
Red Hat Product Errata RHSA-2026:53806 0 None None None 2026-08-11 17:42:19 UTC

Description OSIDB Bzimport 2026-05-21 19:44:43 UTC 
in depth analysis: https://docs.google.com/document/d/1XdX8AJzGjBgCLE0UZ5N_RGGrzQ14HSVS8HcDgH0X70w/edit?tab=t.d440c4doqxdr#bookmark=kix.axzzwc7bbq6o

An external security assessment of Red Hat JBoss EAP 7 identified that the Undertow AJP listener on default port 8009 honours forged ssl_cert and is_ssl AJP attributes without requiring any shared-secret authentication. This enables an unauthenticated attacker with direct TCP access to port 8009 to bypass CLIENT-CERT authentication by injecting a forged X.509 certificate via the AJP protocol.
Comment 1 errata-xmlrpc 2026-08-11 16:37:29 UTC 
This issue has been addressed in the following products:

  Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 7

Via RHSA-2026:53644 https://access.redhat.com/errata/RHSA-2026:53644
Comment 2 errata-xmlrpc 2026-08-11 17:42:17 UTC 
This issue has been addressed in the following products:

  Red Hat JBoss Enterprise Application Platform 7.4.25

Via RHSA-2026:53806 https://access.redhat.com/errata/RHSA-2026:53806
Note You need to log in before you can comment on or make changes to this bug.