CVE-2026-102250
waiting for further signalsZero needs more public information before it can validate it.GHSA-8qvf-7x74-jr2f ↗EUVD-2026-98779 ↗
description
Schneider Electric Sage RTU 1410, 1430, 1450, 2400, 3030 Magnum, and 4400 devices are affected by inadequate verification of firmware authenticity during updates. An attacker able to influence a firmware update initiated by an authorized administrator could install altered firmware and gain control of the device.
mitigation
Restrict firmware-update permissions to necessary administrators, obtain update images only through trusted channels, and verify their integrity before deployment. Isolate affected RTUs from untrusted networks and monitor or approve firmware-update activity until a vendor update is available.
outcome
Contextual: an exploit technique exists, but no deterministic check could cover this one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-10-13 14:51Zcve_org: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/CVE-2026-102250
{ "etk_id": "ETK-2026-1547", "cve_id": "CVE-2026-102250", "display_id": "CVE-2026-102250", "ghsa_id": "GHSA-8qvf-7x74-jr2f", "euvd_id": "EUVD-2026-98779", "status": "published", "anchor_state": "anchored", "title": "Firmware authenticity verification flaw in Schneider Electric Sage RTUs", "summary": "Schneider Electric Sage RTU 1410, 1430, 1450, 2400, 3030 Magnum, and 4400 devices are affected by inadequate verification of firmware authenticity during updates. An attacker able to influence a firmware update initiated by an authorized administrator could install altered firmware and gain control of the device.", "mitigation": "Restrict firmware-update permissions to necessary administrators, obtain update images only through trusted channels, and verify their integrity before deployment. Isolate affected RTUs from untrusted networks and monitor or approve firmware-update activity until a vendor update is available.", "vendor": "Schneider Electric", "product": "Sage RTU 1410", "affected": [ { "affected_notes": [ "All versions prior to version C3414-500-S02L0" ], "affected_ranges": [], "ecosystem": null, "fixed_versions": [], "package_name": "Sage RTU 1410", "purl": null }, { "affected_notes": [ "All versions prior to version C3414-500-S02L0" ], "affected_ranges": [], "ecosystem": null, "fixed_versions": [], "package_name": "Sage RTU 1430", "purl": null }, { "affected_notes": [ "All versions prior to version C3414-500-S02L0" ], "affected_ranges": [], "ecosystem": null, "fixed_versions": [], "package_name": "Sage RTU 1450", "purl": null }, { "affected_notes": [ "All versions prior to version C3414-500-S02L0" ], "affected_ranges": [], "ecosystem": null, "fixed_versions": [], "package_name": "Sage RTU 2400", "purl": null }, { "affected_notes": [ "All versions prior to version C3414-500-S02L0" ], "affected_ranges": [], "ecosystem": null, "fixed_versions": [], "package_name": "Sage RTU 3030 Magnum", "purl": null }, { "affected_notes": [ "All versions prior to version C3414-500-S02L0" ], "affected_ranges": [], "ecosystem": null, "fixed_versions": [], "package_name": "Sage RTU 4400", "purl": null } ], "cwes": [ 345 ], "cvss_score": 8.6, "cvss_src": "cna_vendor", "cvss_vector": "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", "epss_score": 0.0015, "epss_percentile": 0.0396, "epss_asof": "2026-10-20", "automation": "contextual", "check": false, "check_confidence_basis": null, "exploit": false, "pipeline_minutes": 12.8093883, "t0_at": "2026-10-13T14:51:48.442000+00:00", "signals": { "trigger_signal": { "at": "2026-10-13T14:51:48.442000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-10-13T14:51:48.442000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-102250" } } }
published 2026-10-14 06:56Z
last change 2026-10-21 04:45Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.