Bug 2494675 (CVE-2026-55276) - CVE-2026-55276 tomcat: Apache Tomcat: Misleading security logs due to incorrect control flow
Summary: CVE-2026-55276 tomcat: Apache Tomcat: Misleading security logs due to incorre...
Keywords:
Status: NEW
Alias: CVE-2026-55276
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2494717
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-06-29 21:02 UTC by OSIDB Bzimport
Modified: 2026-08-05 13:12 UTC (History)
10 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:49951 0 None None None 2026-08-05 13:12:31 UTC
Red Hat Product Errata RHSA-2026:49952 0 None None None 2026-08-05 13:11:45 UTC

Description OSIDB Bzimport 2026-06-29 21:02:37 UTC 
Always-Incorrect Control Flow Implementation vulnerability in Apache Tomcat meant that special roles and empty authorisation constraints were not included when the effective web.xml was logged.

This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.22, from 10.1.0-M1 through 10.1.55, from 9.0.0.M1 through 9.0.118, from 8.5.0 through 8.5.100. Other versions that have reached end of support may also be affected.

Users are recommended to upgrade to version 11.0.23, 10.1.56 or 9.0.119 which fixes the issue.
Comment 2 errata-xmlrpc 2026-08-05 13:11:44 UTC 
This issue has been addressed in the following products:

  Red Hat JBoss Web Server 7.0.1

Via RHSA-2026:49952 https://access.redhat.com/errata/RHSA-2026:49952
Comment 3 errata-xmlrpc 2026-08-05 13:12:29 UTC 
This issue has been addressed in the following products:

  Red Hat JBoss Web Server 7.0 on RHEL 10
  Red Hat JBoss Web Server 7.0 on RHEL 8
  Red Hat JBoss Web Server 7.0 on RHEL 9

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