Skip to main content
CVE-2026-33818VulnerabilityPublished

Red Hat Security Advisory: Red Hat Openshift Mirror Registry v2.0.13

Affects Red HatSource GCVE Database

0
Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-33818· High 7.5

Not known to be exploited · CVSS 7.5 High · fixed in Red Hat package updates : patch Red Hat asn1 soon.

Data as of 21 Nov 2026, 00:32 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CISA-ADPCVSS 3.17.5
Patch
Available – fixed in 1.27.0-rc.3, 1.26.6, 1.25.13
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade encoding/asn1 to 1.27.0-rc.3, 1.26.6 or 1.25.13.

Affected software

ProductAffectedFixed in
Go standard libraryencoding/asn1Affected
  • >=1.27.0-0 <1.27.0-rc.3
Fixed in
  • 1.27.0-rc.3
Go standard libraryencoding/asn1Affected
  • >=1.26.0-0 <1.26.6
Fixed in
  • 1.26.6
Go standard libraryencoding/asn1Affected
  • <1.25.13
Fixed in
  • 1.25.13
Goencoding/asn1pkg:golang/encoding/asn1Other threatsAffected
  • <1.25.13
  • >=1.26.0-0 <1.26.6
  • >=1.27.0-0 <1.27.0-rc.3
Fixed in
  • 1.25.13
  • 1.26.6
  • 1.27.0-rc.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Red Hat has released fixed versions of Quay that address this vulnerability: 3.9.28, 3.10.28, 3.12.24, 3.14.10, 3.15.9, 3.16.7, 3.17.7, and 3.18.3. Users should update to one of these versions to fully remediate the issue. Red Hat has already fixed Quay.io. There is no complete workaround other than updating. If immediate update is not possible, restrict creation of namespaces containing underscores, rotate robot tokens for namespaces that collide with underscore-containing names, and monitor registry activity for unusual pulls or pushes. These steps reduce exposure but do not fix the underlying flaw.

Description

A critical vulnerability (CVE-2026-110697) in Red Hat Quay, part of the OpenShift Mirror Registry v2.0.13, allows an authenticated attacker to bypass tenant isolation in multi-tenant deployments. The flaw arises from improper escaping of SQL LIKE wildcard characters in namespace names, enabling attackers to steal robot account tokens from other tenants. These stolen tokens can be used to manipulate container images, posing a significant risk to container supply chains. Red Hat has released fixed versions of Quay to address this issue.

References

Community reviews

Loading reviews…