CVE-2026-134651
Awaiting Analysis Awaiting Analysis - Queue

Privilege Escalation in Quay via JWT Authentication Bypass

Vulnerability report for CVE-2026-134651, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-22

Last updated on: 2026-11-22

Assigner: redhat-SADP

Description

A flaw was found in Quay. This vulnerability allows an authenticated remote attacker holding a restricted, short-lived JSON Web Token (JWT) to achieve privilege escalation. Because Quay improperly accepts scoped registry bearer tokens as valid robot account passwords, an attacker can authenticate directly as the robot account and obtain broader permissions. Consequently, unauthorized access persists and enables the attacker to generate fresh tokens even after the robot account's password has been reset.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-22
Last Modified
2026-11-22
Generated
2026-11-22
AI Q&A
2026-11-22
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
Red Hat Red Hat Quay 3 *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-303 The requirements for the product dictate the use of an established authentication algorithm, but the implementation of the algorithm is incorrect.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in Quay allows an authenticated attacker with a restricted JWT to escalate privileges. The system incorrectly accepts scoped registry bearer tokens as valid robot account passwords, letting the attacker authenticate as the robot and obtain broader permissions. This unauthorized access persists even after the robot's password is reset because the attacker can generate new tokens.

Detection Guidance

To detect this vulnerability, monitor Quay logs for unusual robot account authentications using JWT tokens as passwords. Check for repeated failed login attempts followed by successful ones with broader permissions. Inspect `/v2/auth` endpoints for token generation requests from unexpected sources. Verify robot account passwords were not recently reset but still show active sessions.

Impact Analysis

An attacker could gain unauthorized access to repositories or data associated with the compromised robot account. They may perform actions beyond their intended permissions, such as pushing or pulling container images, and maintain access even after password resets. This could lead to data breaches or unauthorized modifications.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating confidentiality requirements in GDPR and HIPAA. Persistent unauthorized access may result in data breaches, triggering reporting obligations and potential fines under these regulations.

Mitigation Strategies

Disable or delete affected robot accounts in Quay. Remove repository permissions for compromised robot accounts. Monitor for unauthorized token generation via /v2/auth endpoints.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-134651. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...