Cross-scope resource access via access-key authorization bypass
Published Jan 29, 2026 · Updated Jan 29, 2026
Incorrect authorization in vCluster Platform before 4.3.10, 4.4.2, 4.5.4, and 4.6.0 allows remote authenticated users to cross access-key scopes. A scoped key is accepted for API requests targeting other projects or virtual clusters instead of enforcing the resource limits stored in the key scope. Exploitation requires a valid scoped access key, and access remains bounded by the permissions of the user who created that key.
Summary
What happened
Incorrect authorization in vCluster Platform before 4.3.10, 4.4.2, 4.5.4, and 4.6.0 allows remote authenticated users to cross access-key scopes. A scoped key is accepted for API requests targeting other projects or virtual clusters instead of enforcing the resource limits stored in the key scope. Exploitation requires a valid scoped access key, and access remains bounded by the permissions of the user who created that key.
The record
- CVE
- CVE-2026-22806
- Published
- Jan 29, 2026
- Updated
- Jan 29, 2026
- Vendor
- vCluster Labs
- Product
- vCluster Platform
- Classifications
- CWE-863, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 29, 2026CVE publishedPublication date reported by the CVE source.
- Jan 29, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.3.10
- Affected versionversion=>= 4.4.0, < 4.4.2
- Affected versionversion=>= 4.5.3, < 4.5.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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