QuayApplication · Redhat
CVE-2025-4374
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceIn Quay, when an organization is configured as a proxy cache and a user or robot account pulls an image that hasn't been mirrored yet, the repository is created automatically. The flaw grants the pulling user Admin permissions on this newly created repository, resulting in unintended privilege escalation where users obtain elevated access they should not have.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
QuayApplication
<= 3.14.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Quay versionQuery the Quay API endpoint /api/v1/superuser/teams or check the container image tag/version to identify if the running version is 3.14.0 or lowerAffected if The installed Quay version is 3.14.0 or earlier
-
Identify proxy cache organizationsQuery the Quay API endpoint /api/v1/organization to list all organizations, then check each organization's proxy cache configuration via /api/v1/organization/{orgname}/proxy-cacheAffected if Any organization has proxy cache configuration enabled or defined
-
Audit repository permissions for recent auto-created reposQuery /api/v1/repository/ to list repositories in proxy cache organizations, then check repository permissions via /api/v1/repository/{namespace}/{repo}/permissions for unexpected admin roles assigned to users or robot accountsAffected if Users or robot accounts have Admin permissions on repositories they did not create manually, particularly in proxy cache organizations
-
Check for unauthorized admin access via user permissions APIQuery /api/v1/superuser/users to list users, then for each user query /api/v1/user/{username}/permissions to enumerate all repositories where they hold Admin roleAffected if Users who should not have admin access are listed as Admins on repositories in proxy cache organizations they did not create
A user is affected if running Quay version 3.14.0 or earlier AND has organizations configured with proxy cache where users have unexpectedly obtained Admin permissions on auto-created repositories.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataFix the permission assignment logic in Quay to ensure users pulling uncached images via proxy cache do not receive Admin permissions on auto-created repositories; consider using read-only or default permissions instead.
Fix this in Quay
Scoped from the published advisory
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-4374 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-4374 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data