CVE-2026-6848 | Red Hat Quay 3 User Interface session expiration
VulDBArchived Apr 22, 2026✓ Full text saved
A vulnerability described as critical has been identified in Red Hat Quay 3 . Affected by this issue is some unknown functionality of the component User Interface . Such manipulation leads to session expiration. This vulnerability is uniquely identified as CVE-2026-6848 . The attack can be launched remotely. No exploit exists.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-358833 · CVE-2026-6848 · GCVE-0-2026-6848
RED HAT QUAY 3 USER INTERFACE SESSION EXPIRATION
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
5.9 $5k-$25k 1.50+
Summaryinfo
A vulnerability classified as critical has been found in Red Hat Quay 3. This affects an unknown part of the component User Interface. Performing a manipulation results in session expiration. This vulnerability was named CVE-2026-6848. The attack may be initiated remotely. There is no available exploit.
Detailsinfo
A vulnerability, which was classified as critical, was found in Red Hat Quay 3. This affects some unknown processing of the component User Interface. The manipulation with an unknown input leads to a session expiration vulnerability. CWE is classifying the issue as CWE-613. According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization." This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
A flaw was found in Red Hat Quay. When Red Hat Quay requests password re-verification for sensitive operations, such as token generation or robot account creation, the re-authentication prompt can be bypassed. This allows a user with a timed-out session, or an attacker with access to an idle authenticated browser session, to perform privileged actions without providing valid credentials. The vulnerability enables unauthorized execution of sensitive operations despite the user interface displaying an error for invalid credentials.
The advisory is shared at access.redhat.com. This vulnerability is uniquely identified as CVE-2026-6848 since 04/22/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 04/22/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Productinfo
Vendor
Red Hat
Name
Quay
Version
3
License
open-source
Website
Vendor: https://www.redhat.com/
CPE 2.3info
🔒
CPE 2.2info
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 5.9
VulDB Meta Temp Score: 5.9
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.4
CNA Vector (redhat): 🔒
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Session expiration
CWE: CWE-613
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: no mitigation known
Status: 🔍
0-Day Time: 🔒
Timelineinfo
04/22/2026 Advisory disclosed
04/22/2026 +0 days CVE reserved
04/22/2026 +0 days VulDB entry created
04/22/2026 +0 days VulDB entry last update
Sourcesinfo
Vendor: redhat.com
Advisory: access.redhat.com
Status: Confirmed
CVE: CVE-2026-6848 (🔒)
GCVE (CVE): GCVE-0-2026-6848
GCVE (VulDB): GCVE-100-358833
Entryinfo
Created: 04/22/2026 12:57
Changes: 04/22/2026 12:57 (61)
Complete: 🔍
Cache ID: 99:CFD:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸