CVE-2026-123710 json
Quay: red hat quay: unauthenticated registry signing-key takeover via service key rotation
published 18h ago modified 18h ago also EUVD-2026-123542
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
A flaw was found in Red Hat Quay. An unauthenticated client can obtain an anonymous registry token with an audience it controls, present that token to the service key rotation endpoint, and install its own approved signing key with no expiry. Registry tokens signed with that key are accepted for any repository, allowing read and write access to private images and replacement of repository tags.
Is CVE-2026-123710 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-123710 updated cvss 9.8
quay: Red Hat Quay: unauthenticated registry signing-key takeover via service key rotation
-
Red Hat Quay 3 quay/quay-rhel8, quay/quay-rhel9 Red Hat Quay 5 quay/quay-rhel9affected: workaround, no fix available
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
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Red Hat Red Hat Quay 3
- Red Hat Red Hat Quay 5
Classification
- Weakness
-
- CWE-1287 Improper Validation of Specified Type of Input
References
-
access.redhat.com
/security/cve/CVE-2026-123710
vdb-entry
-
bugzilla.redhat.com
/show_bug.cgi?id=2568072
issue-tracking
Sources
- CVE List CVE-2026-123710
- NVD CVE-2026-123710
Fencer Intel 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.