# CVE-2025-26499: Race condition in Wind River Studio Developer

> A race condition in Wind River Studio Developer may inadvertently grant one user another user's token, leading to unauthorized access to data and system rights.

- **Severity:** Medium 6.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Sep 2025
- **Updated:** 11 Sep 2025
- **Also known as:** GHSA-fh9m-7jq4-376w

## What is CVE-2025-26499?

CVE-2025-26499 is a medium-severity vulnerability in Wind River Studio Developer, published on 11 Sep 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Under heavy system utilization a random race condition can occur during authentication or token refresh operation. This flaw allows one user to be granted a token intended for another user, resulting in impersonation until the session is ended. This flaw cannot be intentionally exploited due to the required concurring action by two users. However, if the event occurs a user would be inadvertently exposed to another user’s system rights and data access.

Weakness: CWE-270 (Privilege Context Switching Error)

## Which versions are affected by CVE-2025-26499?


## How do I fix CVE-2025-26499?

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

## Is CVE-2025-26499 being exploited?

There is no known exploitation of CVE-2025-26499 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-26499 and fix it if it is affected.

What it is: CVE-2025-26499 is a medium-severity vulnerability in Wind River Studio Developer, published on 11 Sep 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-26499 in the wild and no public exploit code.

Affected product: Wind River Studio Developer. 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-2025-26499/ (Markdown: https://insights.sbomify.com/CVE-2025-26499/index.md)
```

## Sources

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

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