CVE-2025-3449 Weak Session Token used in Automation Runtime SDM
Low 2.3
Published
Updated
Check this codebase for CVE-2025-3449 and fix it if it is affected.
What it is: CVE-2025-3449 is a low-severity vulnerability in B&R Industrial Automation GmbH Automation Runtime, published on 7 Oct 2025.
Exploitation: There is no known exploitation of CVE-2025-3449 in the wild and no public exploit code.
Affected product: B&R Industrial Automation GmbH 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-3449/ (Markdown: https://insights.sbomify.com/CVE-2025-3449/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2025-3449?
CVE-2025-3449 is a low-severity vulnerability in B&R Industrial Automation GmbH Automation Runtime, published on 7 Oct 2025.
Official description
A Generation of Predictable Numbers or Identifiers vulnerability in the SDM component of B&R Automation Runtime versions before 6.4 may allow an unauthenticated network-based attacker to take over already established sessions.
Weakness: CWE-340
Which versions are affected by CVE-2025-3449?
How do I fix CVE-2025-3449?
No fix has been published for CVE-2025-3449 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-3449 being exploited?
There is no known exploitation of CVE-2025-3449 in the wild and no public exploit code.
Sources
Also known as GHSA-6rgw-qfm8-jfvg.