High [CVE-2026-65182] Security constraint bypass due to improper access control
This high-severity Red Hat Linux advisory covers CVE-2026-65182 affecting Red Hat JBoss Web Server 6.2.5, Red Hat JBoss Web Server 6.2 on RHEL 10, Red Hat JBoss Web Server 6.2 on RHEL 8.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Get an email when Red Hat Linux publishes the next one.
VulniPulse checks Red Hat Linux's security advisories around the clock and emails you new ones with the severity, the fixed version and the vendor's link. First month free, then US$15/month; we email you before the first charge.
Summary
Improper Access Control, Incorrect Authorization vulnerability in Apache Tomcat leads to security constraint bypass if a constraint for a longer path is specified before a more restrictive constraint for a shorter sub-path.
This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.24, from 10.1.0-M1 through 10.1.57, from 9.0.0.M1 through 9.0.120, from 8.5.0 through 8.5.100, from 7.0.0 through 7.0.109. Users are recommended to upgrade to version 11.0.25, 10.1.58, 9.0.121, which fixes the issue.
This Important vulnerability in Apache Tomcat allows for security constraint bypasses, potentially granting unauthorized access to protected web application resources. The flaw occurs when security constraints for longer URL paths are defined before more restrictive constraints for shorter, specific sub-paths within the application's `web.xml` configuration.
This misconfiguration can undermine intended access controls in Red Hat deployments of Apache Tomcat. Red Hat severity: Important — CVSS 8.2 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N).
Weakness: CWE-551.
Affected products named by the advisory: Red Hat JBoss Web Server 6.2.5; Red Hat JBoss Web Server 6.2 on RHEL 10; Red Hat JBoss Web Server 6.2 on RHEL 8; Red Hat JBoss Web Server 6.2 on RHEL 9; and 11 more.
- 11.0.0
- 11.0.24
- 10.1.0
- 10.1.57
- 9.0.0
- 9.0.120
- 8.5.0
- 8.5.100
- 7.0.0
- 7.0.109
Official advisory · high-confidence parse· fetched 21 days ago·verify at source
- 11.0.25
- 10.1.58
- 9.0.121
- tomcat
- jws6-tomcat-0:10.1.49-16.redhat_00016.1.el10jws
- jws6-tomcat-0:10.1.49-16.redhat_00016.1.el8jws
- jws6-tomcat-0:10.1.49-16.redhat_00016.1.el9jws
- tomcat11-main-11.0.25-0.1.hum1
- tomcat10-main-10.1.59-0.1.hum1
- RHSA-2026:73982
- RHSA-2026:73981
- RHSA-2026:56039
- RHSA-2026:63137
Official advisory · high-confidence parse· fetched 21 days ago·verify at source
Mitigation checklist
- To mitigate this issue, ensure that security constraints in Apache Tomcat's web.xml configuration files are ordered from most specific to least specific. More restrictive constraints for shorter sub-paths must be defined before broader constraints for longer paths. Incorrect ordering can lead to a bypass of intended access controls. After modifying web.xml, a restart or reload of the Apache Tomcat service is required for the changes to take effect, which may temporarily interrupt service availability.
Official advisory · high-confidence parse· fetched 21 days ago·verify at source
More Red Hat Linux advisories
- CVE-2026-111497Oct 22, 2026Out-of-Bounds Write in Google Brotli Decoder
- CVE-2026-109619Oct 21, 2026fatal error handling retains stale request state leading to use-after-free
- CVE-2026-109618Oct 21, 2026OOM bailout during request parsing leads to memory corruption and RCE
- CVE-2026-34486Apr 9, 2026Missing Encryption of Sensitive Data due to EncryptInterceptor bypass
- CVE-2026-64849Aug 17, 2026Unauthenticated full-read SSRF in webhook delivery: _validate_webhook_url bypassed
- CVE-2026-53362Jul 4, 2026account for fraggap on the paged allocation path
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 34 official vendor sources and 160+ reviewed platform categories.
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.