OpenPLC Runtime v4 Replaces Vulnerable End-of-Life v3

P2 — VALIDATE AND UPDATEMedium · 6.1 (CVSS v3.1) / 5.3 (CVSS v4.0)CISA: NO PUBLIC REPORTS

Quick Answer

OpenPLC Runtime v3 is end of life and has a web-interface cross-site scripting flaw, CVE-2026-88020. CISA relays the vendor recommendation to migrate to v4 because v3 no longer receives security fixes. Treat this as a control-system migration, not an ordinary package patch: limit web-interface exposure now, then validate the v4 program, I/O and recovery behavior offline before an operations-approved cutover.

Confirm Scope And Apply The Supported Fix

What to do now: identify v3 controllers, the processes they operate and every path to their web interfaces. Coordinate network containment and v4 migration with the control-system owner. Preserve the current program/configuration and a documented safe-state recovery plan; do not experiment on an operating physical process.

Open the authoritative advisory

Source recheck: October 2, 2026 UTC, using CISA's CSAF and CNA records after its HTML page could not be retrieved. Recheck the vendor migration guidance before making a control-system change.

Scope And Authority

Product scopeOpenPLC Runtime v3
AdvisoryICSA-26-265-09
CVECVE-2026-88020
Authoritative release date2026-09-22 UTC (CISA CSAF initial release)
Authority revision date2026-09-22 UTC (CISA CSAF v1 current release)
Affected versionsOpenPLC Runtime v3
Fixed versionMigrate to OpenPLC Runtime v4; version 3 is end of life
CVSS base score6.1 (CVSS v3.1) / 5.3 (CVSS v4.0)
CVSS severityMedium
Exploitation statusCISA states that no known public exploitation specifically targeting this issue had been reported to it at issuance. This is not proof that exploitation has never occurred.

What Changed

The web interface uses a query-string value without adequate encoding. CISA warns that successful exploitation could hijack an operator session and permit state-changing requests with consequences for the controlled process. The medium CVSS rating does not establish that a particular plant can tolerate the risk or an unplanned restart.

What To Validate Now

  1. Inventory. Record Runtime version, controller hardware, program/configuration backups, I/O mapping, engineering workstations, web access paths and the accountable operations owner.
  2. Establish applicability. CISA identifies Runtime v3 as affected and the CNA lists v4 as unaffected by this CVE. That is not evidence that an existing v3 program or hardware interface will migrate unchanged.
  3. Remediate. Follow the vendor's v4 migration procedure with compatibility review, a safe maintenance state and an approved recovery path. Network isolation is an interim control; it does not restore support or patch v3.
  4. Validate. On an offline test system, verify control logic, I/O behavior, communications, operator access and recovery. Obtain operations acceptance before live cutover; never use the production controller for XSS reproduction.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Containment and migration can themselves affect availability or safety. Perform the impact assessment with operations staff, preserve independent protective controls and retain the approved safe-state procedure. Avoid an automatic rollback that reconnects an exposed, unsupported v3 controller without a separate risk decision.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.