ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-109195

A flaw was found in Quay.

Published Oct 12, 2026 · catalog updated Oct 15, 2026 · A flaw was found

Check if you run it

No confirmed exploitation is on record for CVE-2026-109195. EPSS is 0.15%. Act only if a listed version of A flaw was found is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (A flaw was found).
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Low3.1
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.15%
Remediation
Advisory link
Affected products
See sources for product scope

A flaw was found in Quay. An authenticated attacker can access repository auto-prune configurations from other namespaces, leading to unauthorized information disclosure. This issue occurs because the application does not properly enforce namespace scoping when retrieving policy details by repository name and policy identifier. To exploit the vulnerability, the attacker must manage a repository sharing the target's name and know the target policy's unique identifier.

No affected version ranges are stored yet. Use the vendor advisory before you decide this record does not apply.

How to fix CVE-2026-109195

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-109195. EPSS is 0.15%. Act only if a listed version of A flaw was found is installed.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-639: Authorization Bypass Through User-Controlled Key. EPSS 0.15%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 12, 2026 · NIST NVD

    Detected

    A flaw was found in Quay. An authenticated attacker can access repository auto-prune configurations from other namespaces, leading to unauthorized information disclosure. This issue occurs because the application does not properly enforce namespace scoping when retrieving policy details by repository name and policy identifier. To exploit the vulnerability, the attacker must manage a repository sh

  2. Oct 14, 2026 · NIST NVD

    Updated

    A flaw was found in Quay. An authenticated attacker can access repository auto-prune configurations from other namespaces, leading to unauthorized information disclosure. This issue occurs because the application does not properly enforce namespace scoping when retrieving policy details by repository name and policy identifier. To exploit the vulnerability, the attacker must manage a repository sh

  3. Oct 15, 2026 · NIST NVD

    Updated

    A flaw was found in Quay. An authenticated attacker can access repository auto-prune configurations from other namespaces, leading to unauthorized information disclosure. This issue occurs because the application does not properly enforce namespace scoping when retrieving policy details by repository name and policy identifier. To exploit the vulnerability, the attacker must manage a repository sh

Sources

  • CVE.orgVulnerability recordCVE-2026-109195

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-109195

    30-day exploitation probability 0.2%

    first.org
  • NIST NVDVulnerability recordCVE-2026-109195

    A flaw was found in Quay. An authenticated attacker can access repository auto-prune configurations from other namespaces, leading to unauthorized information disclosure. This issue occurs because the application does not properly enforce namespace scoping when retrieving policy

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.