Red Hat Single Sign-On 7.6.13 Fixes 27 Vulnerabilities

P1 — VALIDATE AND UPDATEMedium to Critical · 5.3 / 7.2 / 7.4 / 7.5 / 7.7 / 8.1 / 8.3 / 8.7 / 9.6 (CVSS v3.1)EXPLOITATION: NOT STATED

Quick Answer

Red Hat published RHSA-2026:76132 and RHSA-2026:76134 and RHSA-2026:76129 and RHSA-2026:76130 for Red Hat Single Sign-On 7.6.13 packages for RHEL 8 and 9 plus the OpenShift image. Match entitled deployments to the exact advisory relationships, apply Red Hat Single Sign-On 7.6.13 packages for RHEL 8 and 9 and the advisory-listed immutable OpenShift image digests, validate dependent operations, and preserve evidence.

Validate Single Sign-On Scope And Apply The Red Hat Fix

What to do now: Inventory Red Hat Single Sign-On 7.6.13 packages for RHEL 8 and 9 plus the OpenShift image, confirm the exact entitled branch and installed build or digest, apply the advisory-listed content, validate representative services, and document exceptions.

Open the authoritative advisory

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

Scope And Authority

Product scopeRed Hat Single Sign-On 7.6.13 packages for RHEL 8 and 9 plus the OpenShift image
AdvisoryRHSA-2026:76132 / RHSA-2026:76134 / RHSA-2026:76129 / RHSA-2026:76130
CVEsCVE-2025-12543, CVE-2025-14813, CVE-2025-9784, CVE-2026-0603, CVE-2026-15563, CVE-2026-2092, CVE-2026-2575, CVE-2026-3505, CVE-2026-42578, CVE-2026-42579, CVE-2026-42581, CVE-2026-42587, CVE-2026-44249, CVE-2026-44893, CVE-2026-45416, CVE-2026-45674, CVE-2026-4634, CVE-2026-47691, CVE-2026-48043, CVE-2026-48059, CVE-2026-50010, CVE-2026-50193, CVE-2026-54512, CVE-2026-5588, CVE-2026-68494, CVE-2026-7307, CVE-2026-7507
Authoritative release date2026-10-05 18:18:32 UTC
Authority revision date2026-10-06 11:50:58 UTC
Affected versionsThe Red Hat Single Sign-On 7.6 for RHEL 8 and 9 packages and OpenShift image identified as affected in the four advisory product-status relationships.
Fixed versionRed Hat Single Sign-On 7.6.13 packages for RHEL 8 and 9 and the advisory-listed immutable OpenShift image digests
CVSS base score5.3 / 7.2 / 7.4 / 7.5 / 7.7 / 8.1 / 8.3 / 8.7 / 9.6 (CVSS v3.1)
CVSS severityMedium to Critical
Exploitation statusNot stated by the authority; no exploitation claim is inferred.

What Changed

Red Hat expanded the Single Sign-On 7.6.13 release evidence to include RHEL 8 and RHEL 9 packages in addition to the previously published OpenShift image and platform advisory coverage.

What To Validate Now

  1. Inventory. Locate Red Hat Single Sign-On 7.6.13 packages for RHEL 8 and 9 plus the OpenShift image; record the installed build or digest, repository and entitlement, owner, exposure, dependencies, and maintenance group.
  2. Establish applicability. Compare each deployment with the product and fixed-status relationships in RHSA-2026:76132 and RHSA-2026:76134 and RHSA-2026:76129 and RHSA-2026:76130. Do not infer applicability from a component name or CVSS rating alone.
  3. Remediate. Apply Red Hat Single Sign-On 7.6.13 packages for RHEL 8 and 9 and the advisory-listed immutable OpenShift image digests from the supported Red Hat channel for the exact product branch or architecture.
  4. Validate. Confirm the resulting package version or immutable digest, exercise representative Single Sign-On services and recovery paths, monitor for regressions, and record the result.
  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

Back up configuration and databases, stage authentication and federation changes, and validate OIDC, SAML, LDAP, clustering, themes, extensions, and rollback before broad deployment. Preserve pre-change versions or digests, logs, installation output, validation evidence, and rollback decisions.

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.