# CVE-2025-3450: Automation Runtime SDM requests may impact system

> Unauthenticated attackers can exploit improper resource locking in B&R Automation Runtime to delete data and cause denial of service.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Oct 2025
- **Updated:** 8 Oct 2025
- **Also known as:** GHSA-q6v3-r63x-q74w

## What is CVE-2025-3450?

CVE-2025-3450 is a critical vulnerability in B&R Industrial Automation Automation Runtime, published on 7 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An Improper Resource Locking vulnerability in the SDM component of B&R Automation Runtime versions before 6.3 and before Q4.93 may allow an unauthenticated network-based attacker to delete data causing denial of service conditions.

Weakness: CWE-413 (Improper Resource Locking)

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


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

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

## Is CVE-2025-3450 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-3450 is a critical vulnerability in B&R Industrial Automation Automation Runtime, published on 7 Oct 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-3450 in the wild and no public exploit code.

Affected product: B&R Industrial Automation Automation Runtime. 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-3450/ (Markdown: https://insights.sbomify.com/CVE-2025-3450/index.md)
```

## Sources

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

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