A flaw was found in Quay. A user configured in GLOBAL_READONLY_SUPER_USERS is able to view robot account tokens for repositories they are not a member of, allowing an attacker with read-only superuser privileges to impersonate any robot account.
CVE-2026-18255
HIGHPre-NVD 7.27.2—Trending — 3 sources updated this week
EchelonGraph scoreHIGH confidence
Score 7.2 from GitHub Security Advisory (severity: HIGH) published 2026-07-29. a secondary CVSS source baseline 7.2; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
7.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 7.2Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.2
- EG Score
- 7.2(high)
- EG Risk
- 32(Track)EG Risk 32/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity72% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
July 29, 2026
Last Modified
July 29, 2026
Advisory Details (2)
Auto-updated Jul 29, 2026Patch available. Sources: redhat.
redhat
2508454 – (CVE-2026-18255) CVE-2026-18255 quay: quay: Global read-only superuser can view robot account tokens
https://bugzilla.redhat.com/show_bug.cgi?id=2508454Vendor Advisories for CVE-2026-18255(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-30 08:34 UTCGHSA enrichment
- 2026-07-29 19:33 UTCEG score recompute
- 2026-07-29 19:32 UTCGHSA enrichment
- 2026-07-29 18:34 UTCEG score recompute
- 2026-07-29 18:34 UTCGHSA enrichment
- 2026-07-29 17:26 UTCEG score recompute
- 2026-07-29 16:38 UTCEG score recompute
- 2026-07-29 16:37 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-863
Frequently asked(4)
What is CVE-2026-18255?
CVE-2026-18255 is a high vulnerability published on July 29, 2026. A flaw was found in Quay. A user configured in GLOBALREADONLYSUPER_USERS is able to view robot account tokens for repositories they are not a member of, allowing an attacker with read-only superuser privileges to impersonate any robot account.
When was CVE-2026-18255 disclosed?
CVE-2026-18255 was first published in the National Vulnerability Database on July 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-18255?
CVE-2026-18255 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2026-18255?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18255, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-18255
Is Your Infrastructure Affected by CVE-2026-18255?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.