Low [CVE-2026-55276] Misleading security logs due to incorrect control flow
This low-severity Red Hat Linux advisory covers CVE-2026-55276 affecting 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.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
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.
This could lead to a security oversight where administrators might misinterpret the actual authorization constraints, potentially impacting the security posture of the application. When the effective web.xml logging feature is enabled for debugging, special roles and empty authorization constraints may be omitted from the logged output.
This is a logging-only issue with no runtime security impact — it only affects the accuracy of debug log output for administrators reviewing the effective web.xml configuration. Red Hat severity: Low — CVSS 2.3 (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N).
Weakness: CWE-778.
Affected products named by the advisory: 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; Red Hat Hardened Images; and 10 more.
- 11.0.0
- 11.0.22
- 10.1.0
- 10.1.55
- 9.0.0
- 9.0.118
- 8.5.0
- 8.5.100
Official advisory · high-confidence parse· fetched 13 days ago·verify at source
- 11.0.23
- 10.1.56
- 9.0.119
- jws7-tomcat-0:11.0.21-6.redhat_00005.1.el10jws
- jws7-tomcat-0:11.0.21-6.redhat_00005.1.el8jws
- jws7-tomcat-0:11.0.21-6.redhat_00005.1.el9jws
- tomcat10-main-10.1.56-1.hum1
- tomcat11-main-11.0.23-0.1.hum1
- RHSA-2026:49951
- RHSA-2026:29203
- RHSA-2026:32960
Official advisory · high-confidence parse· fetched 13 days ago·verify at source
Mitigation checklist
- This is a logging-only issue with no runtime security impact. No mitigation is required. Administrators should not rely solely on the effective web.xml debug log output to verify security constraint configuration.
Official advisory · high-confidence parse· fetched 13 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.