# CVE-2026-35383: Bentley Systems iTwin Platform exposed access token

> An exposed Cesium ion access token allowed unauthenticated attackers to enumerate or delete assets in the iTwin Platform.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Apr 2026
- **Updated:** 14 Apr 2026
- **Also known as:** GHSA-3467-w26x-74wv

## What is CVE-2026-35383?

CVE-2026-35383 is a medium-severity vulnerability in Bentley Systems iTwin Platform, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Bentley Systems iTwin Platform exposed a Cesium ion access token in the source of some web pages. An unauthenticated attacker could use this token to enumerate or delete certain assets. As of 2026-03-27, the token is no longer present in the web pages and cannot be used to enumerate or delete assets.

Weakness: CWE-540 (Inclusion of Sensitive Information in Source Code)

## Which versions are affected by CVE-2026-35383?


## How do I fix CVE-2026-35383?

No fix has been published for CVE-2026-35383 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-35383 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35383 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-35383 and fix it if it is affected.

What it is: CVE-2026-35383 is a medium-severity vulnerability in Bentley Systems iTwin Platform, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35383 exists.

Affected product: Bentley Systems iTwin Platform. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-35383/ (Markdown: https://insights.sbomify.com/CVE-2026-35383/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-35383
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-35383
- OSV: https://osv.dev/vulnerability/CVE-2026-35383

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-35383/
Summaries are generated and may contain mistakes; the official description above is the record.