# CVE-2026-85639: jofpin trape Telemetry Endpoint user.py race condition

> A race condition in the Trape telemetry endpoint allows remote attackers to manipulate user data, though exploitation is highly complex.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Sep 2026
- **Updated:** 10 Sep 2026
- **Also known as:** GHSA-9m9p-mg4g-r54c

## What is CVE-2026-85639?

CVE-2026-85639 is a medium-severity vulnerability in jofpin trape, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A security vulnerability has been detected in jofpin trape 2.0. This vulnerability affects unknown code of the file core/user.py of the component Telemetry Endpoint. Such manipulation of the argument vId leads to race condition. The attack can be executed remotely. Attacks of this nature are highly complex. It is stated that the exploitability is difficult. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

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


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

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

## Is CVE-2026-85639 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85639 is a medium-severity vulnerability in jofpin trape, published on 4 Sep 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-85639 exists.

Affected product: jofpin trape. 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-85639/ (Markdown: https://insights.sbomify.com/CVE-2026-85639/index.md)
```

## Sources

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

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