Red Hat JBoss Web Server 6.2.5 Addresses Thirteen Vulnerabilities

P1 — VALIDATE AND UPDATELow to High · 2.3–8.2 (official CVSS v3.1 range)EXPLOITATION: NOT STATED

Quick Answer

The authority published RHSA-2026:73981 for Red Hat JBoss Web Server 6.2 on RHEL 8, 9, and 10. Red Hat published JBoss Web Server 6.2.5 with the advisory-specific corrected packages or signed container-image digests for the listed CVEs. Affected deployments should be matched to the authority's exact scope and moved to the supported fixed release.

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.

Open the authoritative advisory

Last verified: 2026-10-02 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeRed Hat JBoss Web Server 6.2 on RHEL 8, 9, and 10
AdvisoryRHSA-2026:73981
CVEsCVE-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 date2026-10-01 23:03:51 UTC
Authority revision date2026-10-01 23:42:12 UTC
Affected versionsRed Hat JBoss Web Server 6.2 builds before the 6.2.5 release and advisory-listed packages.
Fixed versionRed Hat JBoss Web Server 6.2.5, including jws6-tomcat 10.1.49-16.redhat_00016.1 for the matching RHEL stream
CVSS base score2.3–8.2 (official CVSS v3.1 range)
CVSS severityLow to High
Exploitation statusNot stated by the authority; no exploitation claim is inferred.

What Changed

Red Hat published JBoss Web Server 6.2.5 with the advisory-specific corrected packages or signed container-image digests for the listed CVEs.

What To Validate Now

  1. 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.
  2. 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.
  3. Remediate. Use the supported Red Hat channel to deploy Red Hat JBoss Web Server 6.2.5, including jws6-tomcat 10.1.49-16.redhat_00016.1 for the matching RHEL stream. For containers, pin and verify the exact signed digest listed for the matching architecture and accelerator variant.
  4. Validate. Confirm the installed package build or running image digest, restart or redeploy affected workloads as required, validate application, cluster, accelerator, and recovery workflows, and record exceptions.
  5. 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

Confirm entitlement and branch support, test package or image compatibility, drain and redeploy clustered workloads deliberately, preserve prior digests and rollback evidence, and do not infer exploitation from severity.

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.