Skip to content
Fencer Vulns
medium 6.5

CVE-2025-4374 json

Quay: incorrect privilege assignment

published 2025-05-06 18 mo ago modified 2026-08-07 3 mo ago also EUVD-2025-13599

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 28%
public exploits
0
none known

Summary

A flaw was found in Quay. When an organization acts as a proxy cache, and a user or robot pulls an image that hasn't been mirrored yet, they are granted "Admin" permissions on the newly created repository.

Patch / fix

  • Project Quay quay 3.11.11, 3.12.10, 3.14.2
  • Red Hat Red Hat Quay 3 v3.11.11-1, v3.11.11-2, v3.11.11-5, v3.11.11-7, v3.12.10-1, v3.12.10-2, v3.12.10-3, v3.12.10-4, v3.13.6-1, v3.13.6-2, v3.13.6-5, v3.13.6-6, v3.14.2-1, v3.14.2-6, v3.14.2-7

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-4374 updated cvss 6.5

quay: Incorrect Privilege Assignment

  • Red Hat Quay v3 quay/quay-rhel8 v3.13.6-5, quay/quay-rhel8 v3.14.2-7, quay/clair-rhel8 v3.13.6-1, quay/clair-rhel8 v3.14.2-1, quay/quay-rhel8 v3.11.11-5, quay/quay-rhel8 v3.12.10-3, +34 more
    fixed: vendor fix “Permissions can be updated after creation but there's no preventative measure before hand.” RHBA-2025:8687

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
18 mo ago

Exploit prediction

0.34% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Affected products

  • Project Quay quay
  • Red Hat Red Hat Quay 3

Classification

Weakness
  • CWE-266 Incorrect Privilege Assignment

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.