# CVE-2025-46613: Race condition in OpenPLC

> A race condition in OpenPLC allows attackers to trigger memory corruption, potentially leading to code execution or denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Apr 2025
- **Updated:** 25 Apr 2025
- **Also known as:** GHSA-5vjg-4vv4-p3vj

## What is CVE-2025-46613?

CVE-2025-46613 is a high-severity vulnerability in openplcproject OpenPLC, published on 25 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenPLC 3 through 64f9c11 has server.cpp Memory Corruption because a thread may access handleConnections arguments after the parent stack frame becomes unavailable.

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

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


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

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

## Is CVE-2025-46613 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-46613 is a high-severity vulnerability in openplcproject OpenPLC, published on 25 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-46613 in the wild and no public exploit code.

Affected product: openplcproject OpenPLC. 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-46613/ (Markdown: https://insights.sbomify.com/CVE-2025-46613/index.md)
```

## Sources

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

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