Security readout for executives and security teams
Plain-English summary
vCluster Platform access keys meant to be limited can access resources outside their assigned scope. An attacker still needs access to a key and cannot exceed the key owner’s permissions, but the bug can break tenant and automation boundaries in Kubernetes management environments.
Executive priority
Treat as urgent for environments relying on scoped access keys for tenant separation or automation safety. Prioritize upgrading and key review because a control intended to limit access may fail, potentially exposing Kubernetes resources within the key owner’s authority.
Technical view
CVE-2026-22806 is a CWE-863 authorization flaw in vCluster Platform/Loft before fixed releases 4.6.0, 4.5.4, 4.4.2, and 4.3.10. Scoped access keys can have their scope bypassed. CVSS is 9.1 due to network reachability, low complexity, changed scope, and high impact ratings.
Likely exposure
Organizations using vCluster Platform access keys with limited scopes are the primary exposure. Risk is highest where keys are shared, used for automation, or owned by users with broad permissions. The provided affected-version data has inconsistencies, so confirm installed versions against vendor guidance.
Exploitation context
The source bundle does not report active exploitation, and KEV status is false. Exploitation requires possession or use of an access key and is bounded by the permissions of that key’s owner. The issue is still serious because scoped controls may not enforce intended isolation.
Researcher notes
Public details are limited to the advisory-level description. The affected-version list in the bundle appears inconsistent for the 4.5 branch, while the description names fixed versions. Do not assume exploit availability. Focus validation on version confirmation, scoped key inventory, owner permissions, and vendor advisory updates.
Mitigation direction
- Upgrade to vCluster Platform fixed versions: 4.6.0, 4.5.4, 4.4.2, or 4.3.10.
- Review scoped access keys and confirm holders have appropriate permissions.
- Use automation users with very limited permissions for access keys if upgrading is delayed.
- Check the GitHub advisory for any additional vendor mitigations or updated affected-version details.
Validation and detection
- Inventory vCluster Platform or Loft deployments and record exact versions.
- Identify access keys configured with limited scopes.
- Review each scoped key owner’s effective permissions.
- Confirm upgraded instances report a fixed version listed by the vendor.
- Monitor vendor advisory updates for corrected version-range details.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-22806 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H2.36Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/loft-sh/loft/security/advisories/GHSA-c539-w4ch-7wxqCVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.