# CVE-2026-102250: Other in Sage RTU 1410

> An authorized admin can upload modified firmware due to insufficient verification, allowing attackers to gain control over the device.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-8qvf-7x74-jr2f

## What is CVE-2026-102250?

CVE-2026-102250 is a high-severity vulnerability in Schneider Electric Sage RTU 1410, published on 13 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

CWE-345: Insufficient Verification of Data Authenticity vulnerability exists that could allow modified firmware to be uploaded when an authorized admin user begins a firmware update procedure which could result in control over the device.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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


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

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

## Is CVE-2026-102250 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-102250 is a high-severity vulnerability in Schneider Electric Sage RTU 1410, published on 13 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-102250 in the wild and no public exploit code.

Affected product: Schneider Electric Sage RTU 1410. 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-102250/ (Markdown: https://insights.sbomify.com/CVE-2026-102250/index.md)
```

## Sources

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

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