Red Hat Quay 3.16.6 Addresses 42 Vulnerabilities

P1 — VALIDATE AND UPDATEMedium to Critical · 5.3 / 6.5 / 6.8 / 7.2 / 7.4 / 7.5 / 7.8 / 8.1 / 8.2 / 9.1 (CVSS v3.1)EXPLOITATION: NOT STATED

Quick Answer

The authority published RHSA-2026:69255 for Red Hat Quay 3.16. Red Hat published a Quay security update with branch-specific fixed content 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 Quay 3.16, 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-09-21 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeRed Hat Quay 3.16
AdvisoryRHSA-2026:69255
CVEsCVE-2026-13149, CVE-2026-15792, CVE-2026-15927, CVE-2026-16221, CVE-2026-18255, CVE-2026-32283, CVE-2026-33818, CVE-2026-39822, CVE-2026-44705, CVE-2026-49477, CVE-2026-54058, CVE-2026-54060, CVE-2026-54770, CVE-2026-55379, CVE-2026-55380, CVE-2026-56852, CVE-2026-56853, CVE-2026-56858, CVE-2026-56859, CVE-2026-56860, CVE-2026-56862, CVE-2026-57231, CVE-2026-59197, CVE-2026-59199, CVE-2026-59200, CVE-2026-59204, CVE-2026-59205, CVE-2026-59869, CVE-2026-59879, CVE-2026-59885, CVE-2026-59886, CVE-2026-67213, CVE-2026-67214, CVE-2026-67313, CVE-2026-67314, CVE-2026-67320, CVE-2026-67321, CVE-2026-69152, CVE-2026-73086, CVE-2026-75593, CVE-2026-82417, CVE-2026-84375
Authoritative release date2026-09-21 08:25:12 UTC
Authority revision date2026-09-21 11:53:24 UTC
Affected versionsThe advisory-specific supported Red Hat Quay 3.16 builds before the listed fixed package or release.
Fixed versionRed Hat Quay 3.16.6
CVSS base score5.3 / 6.5 / 6.8 / 7.2 / 7.4 / 7.5 / 7.8 / 8.1 / 8.2 / 9.1 (CVSS v3.1)
CVSS severityMedium to Critical
Exploitation statusNot stated by the authority; no exploitation claim is inferred.

What Changed

Red Hat published a Quay security update with branch-specific fixed content for the listed CVEs.

What To Validate Now

  1. Inventory. Locate Red Hat Quay 3.16 deployments, versions, enabled features, exposure paths, owners, and dependent services.
  2. Establish applicability. Compare each deployment with the authority's affected-version statement: The advisory-specific supported Red Hat Quay 3.16 builds before the listed fixed package or release. Do not infer applicability from product family or severity alone.
  3. Remediate. Apply Red Hat Quay 3.16.6 through the supported vendor or project channel, following the current advisory and change-control requirements.
  4. Validate. Confirm the resulting version or managed-service state, exercise representative functionality and recovery paths, monitor for regressions, and document 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

Use the exact supported release stream and repository. Test dependencies, clusters, integrations, and rollback before broad deployment; a CVSS rating or reachable feature is not evidence of exploitation.

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.