# CVE-2025-47735: wgp race condition in inner::drop

> A race condition in the wgp Rust crate's drop implementation can lead to thread synchronization issues, potentially causing crashes or undefined behavior.

- **Severity:** Low 2.9 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 May 2025
- **Updated:** 9 May 2025
- **Also known as:** GHSA-2w4w-4385-vh4h

## What is CVE-2025-47735?

CVE-2025-47735 is a low-severity vulnerability in Nugine wgp, published on 9 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

inner::drop in inner.rs in the wgp crate through 0.2.0 for Rust lacks drop_slow thread synchronization.

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

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

2 open source packages ship an affected version, including wgp. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wgp` | crates.io | All versions to 0.2.0 | None |
| `wgp` | crates.io | All versions to 0.2.0 | None |

Products: Nugine Wgp.

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

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

## Is CVE-2025-47735 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-47735 is a low-severity vulnerability in Nugine wgp, published on 9 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-47735 exists.

Affected packages and fixed versions:
- wgp (crates.io): affected all versions up to 0.2.0; no fix listed
- wgp (crates.io): affected all versions up to 0.2.0; no fix listed

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-47735/ (Markdown: https://insights.sbomify.com/CVE-2025-47735/index.md)
```

## Sources

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

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