Approved changes feed: RSS · Atom
cpe:2.3:a:loft-sh:loft:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Loft Sh (78e354c4-7779-590c-8cd0-ed22c635dada) |
|---|---|
| Product | Loft (19d74392-cab2-5426-94e9-eb285085bfbe) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-42457 |
vulnerable | 2026-06-08 08:03:16.326349 |
vCluster Platform: Stored XSS can lead to privilege escalation
CRITICAL (9)
vCluster Platform provides a Kubernetes platform for managing virtual clusters, multi-tenancy, and cluster sharing. Prior to 4.4.3, 4.5.5, 4.6.2, 4.7.1, and 4.8.0, there is a Stored XSS attack vulnerability via the name field of a templateRef. This can lead to the execution of arbitrary external scripts within the platform's browser context. In the worst case, a malicious user could potentially create a new Global-Admin user, bypassing other security restrictions. The attacker needs the ability to create namespaces. This vulnerability is fixed in 4.4.3, 4.5.5, 4.6.2, 4.7.1, and 4.8.0.
Published: 2026-05-14T14:48:05.096Z
Updated: 2026-05-14T19:51:50.476Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-22806 |
vulnerable | 2026-06-08 07:51:13.964834 |
vCluster Platform's Access Keys Allows Access Beyond Scope
CRITICAL (9.1)
vCluster Platform provides a Kubernetes platform for managing virtual clusters, multi-tenancy, and cluster sharing. Prior to versions 4.6.0, 4.5.4, 4.4.2, and 4.3.10, when an access key is created with a limited scope, the scope can be bypassed to access resources outside of it. However, the user still cannot access resources beyond what is accessible to the owner of the access key. Versions 4.6.0, 4.5.4, 4.4.2, and 4.3.10 fix the vulnerability. Some other mitigations are available. Users can limit exposure by reviewing access keys which are scoped and ensuring any users with access to them have appropriate permissions set. Creating automation users with very limited permissions and using access keys for these automation users can be used as a temporary workaround where upgrading is not immediately possible but scoped access keys are needed.
Published: 2026-01-29T19:54:37.810Z
Updated: 2026-01-29T21:19:58.653Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.