CVE-2026-134651 in Quayinfo

Summary

by MITRE • 11/22/2026

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.

Once again VulDB remains the best source for vulnerability data.

Analysis

by VulDB Data Team • 11/22/2026

The vulnerability identified in Quay represents a critical authentication bypass mechanism that exploits improper validation of scoped registry bearer tokens when used for robot account authentication. In typical container image registries, security relies on strict separation between user identities and service accounts, often referred to as robots or bots. These entities are designed with limited permissions to minimize the blast radius of potential compromises. However, in this specific flaw, Quay fails to distinguish between a standard password-based login for a robot account and an authentication attempt using a scoped JWT issued by another entity. This architectural oversight allows an attacker who possesses even a restricted, short-lived JSON Web Token to leverage it as if it were the static secret credential associated with a high-privilege robot account. By submitting this token in place of the expected password during the authentication handshake, the system incorrectly validates the request and grants access under the identity of the targeted robot account rather than the original owner of the JWT or an anonymous state.

This misconfiguration leads directly to privilege escalation, as robot accounts are frequently configured with broader permissions than standard user accounts to facilitate automated CI/CD pipelines and deployment workflows. When an attacker successfully authenticates as a robot account, they inherit all associated privileges, which may include read access to private repositories, write access for pushing images, or even administrative capabilities depending on the organization's configuration. The operational impact is severe because it allows unauthorized actors to infiltrate the container supply chain. Once inside with elevated permissions, an attacker can pull sensitive internal application images containing source code secrets, push malicious backdoored images to be deployed in production environments, or delete critical repository data causing denial of service. This undermines the integrity and confidentiality guarantees that organizations rely on when using private registries for secure software delivery.

A particularly dangerous aspect of this vulnerability is its persistence mechanism relative to credential rotation. Because the attacker authenticates directly as the robot account rather than exploiting a session token that expires, they maintain control over the compromised identity even after administrators detect the breach and reset the robot's password. The flaw lies in the fact that the authentication logic accepts the scoped JWT for login purposes, meaning any new tokens generated by the system under the guise of the robot account will also be valid to the attacker if they can trigger token generation or reuse existing mechanisms within their session scope. This makes remediation difficult because simply changing passwords does not immediately revoke access; instead, it requires invalidating all active sessions and potentially rotating associated API keys or tokens linked to that identity to fully mitigate the risk.

From a standards perspective, this vulnerability aligns with CWE-287 Improper Authentication, specifically where an attacker is able to assume another user's privileges due to flawed credential validation logic. It also maps to MITRE ATT&CK technique T1078 Valid Accounts, as the adversary leverages legitimate but misused credentials (the robot account) to maintain persistence and escalate privileges within the system environment. The exploitation path resembles aspects of CWE-294 Acceptance of Authenticated But Untrusted Clients in certain contexts where trust boundaries are not strictly enforced between different token types. To mitigate this issue, vendors must enforce strict type checking on authentication credentials, ensuring that scoped registry bearer tokens cannot be substituted for static passwords during login procedures. Organizations should also implement least privilege principles by restricting robot account permissions to only what is absolutely necessary and monitoring for anomalous authentication patterns where JWTs are used in unexpected contexts. Regular audits of access control policies and immediate revocation of all active sessions upon any suspected compromise are essential defensive measures until the underlying code flaw is patched.

Responsible

Redhat

Reservation

11/21/2026

Disclosure

11/22/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Interested in the pricing of exploits?

See the underground prices here!