Red Hat JBoss Web Server 6.2.5 Addresses Thirteen Vulnerabilities
Tech GuruQuick Answer
Red Hat JBoss Web Server 6.2.5 replaces 6.2.4 and fixes thirteen Tomcat-related vulnerabilities for the listed RHEL 8, 9 and 10 streams. Match the full supported package build, including the RHEL-specific suffix. The upstream-looking Tomcat version alone does not identify Red Hat's backported fix level.
Confirm Scope And Apply The Supported Fix
What to do now: Inventory Red Hat JBoss Web Server 6.2 on RHEL 8, 9, and 10, match the exact affected release or feature, apply the authority-supported fixed build or service remediation, validate the dependent workflow, and preserve evidence.
Last verified: 2026-10-02 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | Red Hat JBoss Web Server 6.2 on RHEL 8, 9, and 10 |
|---|---|
| Advisory | RHSA-2026:73981 |
| CVEs | CVE-2026-53434, CVE-2026-55276, CVE-2026-59083, CVE-2026-65182, CVE-2026-65183, CVE-2026-65905, CVE-2026-65927, CVE-2026-66299, CVE-2026-66422, CVE-2026-68525, CVE-2026-68569, CVE-2026-68763, CVE-2026-73180 |
| Authoritative release date | 2026-10-01 23:03:51 UTC |
| Authority revision date | Latest current_release_date in the checked advisory set: 2026-10-02T17:35:27+00:00. Individual advisories may have earlier revisions. |
| Affected versions | Red Hat JBoss Web Server 6.2 builds before the 6.2.5 release and advisory-listed packages. |
| Fixed version | Red Hat JBoss Web Server 6.2.5, including jws6-tomcat 10.1.49-16.redhat_00016.1 for the matching RHEL stream |
| CVSS base score | 2.3–8.2 (official CVSS v3.1 range) |
| CVSS severity | Low to High |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
The set covers authorization and authentication boundaries, RewriteValve handling, HTTP/2 allocation leaks and WebSocket behavior after HTTP-session termination. Conditions differ: the CRL issue applies to the FFM connector with Java 22+ and CRL checking; one security-log issue has no runtime security impact. Do not treat all thirteen as equally reachable in every application.
What To Validate Now
- Inventory. Locate Red Hat JBoss Web Server 6.2 on RHEL 8, 9, and 10 deployments, versions, enabled features, exposure paths, owners, and dependent services.
- Establish applicability. Match entitlement, product stream, architecture, source package or image repository, and each advisory's product status. Do not apply one branch's build or digest to another branch.
- Remediate. Apply prerequisite errata and the complete supported JWS 6.2.5 update for the installed RHEL stream. Preserve server configuration, application deployments and connector settings, and coordinate traffic draining/restart where required. Do not replace vendor Tomcat JARs individually with arbitrary upstream files.
- Validate. Verify installed package builds and the restarted service. Check representative applications, TLS connectors, authorized versus denied requests and login/logout behavior, including WebSocket sessions where used. Validate effective behavior rather than relying only on a debug log that prints security constraints.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Review the configured authentication realms, RewriteValve and optional examples before selecting temporary mitigations. Disabling an authentication method or protocol can break applications and is not a universal substitute for the update. No application compatibility or performance test was run here.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
