EM-20261111-1357
VulnerabilityCritical severity
Critical quay Vulnerability (CVE-2026-123710)
CVE-2026-123710
Status
Developing
Since : signals keep joining.
- First Signal
- Nov 11 14:00 UTCC41 Red Hat Security Data
- Page Born
- Nov 11 15:17 UTCsecond source joined
- Last Signal
- Nov 11 15:17 UTC11 hours before snapshot
- Sources
- 21 official · 1 research, news or crowd
- Open For
- 11 hoursso far
Life Of This Page
- 1BornA second, independent source names it.
- 2Developing · NowNew signals join; severity can move.
- 3ConfirmedNot yetCISA KEV lists it, or exploitation in the wild is reported.
- 4ResolvedNot yetPast the fix deadline and 14 days with no new signal.
- 5ArchivedNot yet30 days after resolved. Read only; the link keeps working. Reopens if it comes back.
The ID never changes, and earlier addresses keep working. A correction is logged, never overwritten. If two pages turn out to be one incident, the later one points to the earlier.
Vulnerability Lifecycle
- Disclosed: reachedNov 11 15:17 UTCC6 NVD published
- Scored: reachedNov 11 15:17 UTCCVSS 9.8
- Exploited: not yetNot yetNo exploitation reported
- Advisories: not yetNot yetNone yet
- Vendor Response: reachedNov 11 14:00 UTCC41 published
- Resolved: not yetNot yetAfter 14 quiet days
Timeline
Point at a mark to read it. Squares are signals, colored by severity; every one is also listed under Signals.
Signals
- CVE-2026-123710 (CVSS 9.8) (opens source in a new tab) 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… Crit severityDatabaseC6 NVD CVE API 2.0
- Red Hat: CVE-2026-123710 (critical) (opens source in a new tab) quay: Red Hat Quay: unauthenticated registry signing-key takeover via service key rotation Crit severityVendorC41 Red Hat Security Data