CVE REMEDIATION GUIDE
Review reviewHighFixed-version data available

CVE-2026-9650 remediation guide

Schneider Electric EasyLogic T150 (formerly Saitel DR) Remote Terminal Unit & Controller, Saitel DP Remote Terminal Unit & Controller, easylogic t150 firmware

CWE-522 Insufficiently Protected Credentials vulnerability that could cause unauthorized access and exposure of sensitive information when unauthenticated attacker accesses credentials stored within firmware or system files. With this credential an attacker could subsequently compromise the device if they have physical access to the device.

Open CVE record
ProductSchneider Electric EasyLogic T150 (formerly Saitel DR) Remote Terminal Unit & Controller, Saitel DP Remote Terminal Unit & Controller, easylogic t150 firmware
Affected versions>= Version 11.06.30 and prior, >= Version 11.06.35 and prior, < 11.06.32, < 11.06.38
Fixed versions11.06.32, 11.06.38
Priority basisReview · CVSS 8.7 · EPSS 0.24%
01

Identify the affected asset

Confirm whether Schneider Electric EasyLogic T150 (formerly Saitel DR) Remote Terminal Unit & Controller, Saitel DP Remote Terminal Unit & Controller, easylogic t150 firmware is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= Version 11.06.30 and prior, >= Version 11.06.35 and prior, < 11.06.32, < 11.06.38. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 11.06.32, 11.06.38. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.