Authenticated privileged actions via ignored re-authentication failure
Published Apr 22, 2026 · Updated Apr 22, 2026
Authentication bypass in Red Hat Quay 3 allows remote authenticated users to perform sensitive actions after session timeout. Affected old and new UI endpoints continue executing token generation and robot account creation after password re-verification rejects invalid credentials. Exploitation requires a timed-out session or access to an idle authenticated browser session, and resulting actions use that account's privileges.
Summary
What happened
Authentication bypass in Red Hat Quay 3 allows remote authenticated users to perform sensitive actions after session timeout. Affected old and new UI endpoints continue executing token generation and robot account creation after password re-verification rejects invalid credentials. Exploitation requires a timed-out session or access to an idle authenticated browser session, and resulting actions use that account's privileges.
The record
- CVE
- CVE-2026-6848
- Published
- Apr 22, 2026
- Updated
- Apr 22, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Quay
- Classifications
- CWE-613, T1098
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 22, 2026CVE publishedPublication date reported by the CVE source.
- Apr 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo