Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-34226: CWE-664 Improper Control of a Resource Through Its Lifetime in Autonomy Logic OpenPLC Runtime

0
High
VulnerabilityCVE-2025-34226cvecve-2025-34226cwe-664cwe-20
Published: Fri Oct 03 2025 (10/03/2025, 15:36:03 UTC)
Source: CVE Database V5
Vendor/Project: Autonomy Logic
Product: OpenPLC Runtime

Description

OpenPLC Runtime v3 contains an input validation flaw in the /upload-program-action endpoint: the epoch_time field supplied during program uploads is not validated and can be crafted to induce corruption of the programs database. After a successful malformed upload the runtime continues to operate until a restart; on restart the runtime can fail to start because of corrupted database entries, resulting in persistent denial of service requiring complete rebase of the product to recover. This vulnerability was remediated by commit 095ee09.

AI-Powered Analysis

AILast updated: 11/13/2025, 23:12:37 UTC

Technical Analysis

CVE-2025-34226 is a vulnerability classified under CWE-664 (Improper Control of a Resource Through Its Lifetime) and CWE-20 (Improper Input Validation) affecting Autonomy Logic's OpenPLC Runtime version 3.0. The issue arises from insufficient validation of the epoch_time field submitted via the /upload-program-action endpoint during program uploads. An attacker with low-level privileges can craft a malformed epoch_time value that corrupts the internal programs database. While the runtime continues to function normally immediately after the upload, the corruption manifests upon the next restart, causing the runtime to fail to initialize due to database inconsistencies. This results in a persistent denial of service condition that cannot be resolved without a complete rebase (reinstallation or restoration) of the product, leading to significant operational downtime. The vulnerability does not require user interaction and can be exploited remotely over the network, as indicated by the CVSS vector (AV:N/AC:L/PR:L/UI:N). The severity is rated high with a CVSS 4.0 score of 7.1, reflecting the high impact on availability and the relatively low complexity of exploitation. Although no public exploits are known, the vulnerability poses a critical risk to industrial environments relying on OpenPLC for automation and control. The issue was addressed in a code commit (095ee09), but systems running unpatched versions remain vulnerable.

Potential Impact

For European organizations, particularly those in industrial sectors such as manufacturing, energy, and critical infrastructure that utilize OpenPLC Runtime for automation control, this vulnerability presents a significant threat. Exploitation can lead to persistent denial of service, causing operational disruptions, production downtime, and potential safety hazards if control systems fail unexpectedly. The need for a full product rebase to recover increases recovery time and costs. Given the critical nature of industrial control systems and their role in essential services, such downtime could have cascading effects on supply chains and service delivery. Additionally, the vulnerability could be leveraged as part of a broader attack campaign targeting industrial environments, increasing the risk of economic and reputational damage. The fact that exploitation requires only low privileges but no user interaction means insider threats or attackers who gain limited access could trigger the issue remotely, complicating defense efforts.

Mitigation Recommendations

European organizations should immediately verify their OpenPLC Runtime version and apply the patch containing commit 095ee09 to remediate the vulnerability. Where patching is not immediately feasible, organizations should implement strict network segmentation and access controls to limit access to the /upload-program-action endpoint, restricting it to trusted administrators only. Employ input validation proxies or web application firewalls (WAFs) that can detect and block malformed epoch_time values. Regularly back up the programs database to enable rapid restoration in case of corruption. Monitor system logs and network traffic for unusual upload activities or failed restarts indicative of exploitation attempts. Conduct security awareness training for personnel with upload privileges to prevent accidental misuse. Finally, integrate vulnerability scanning and automated compliance checks into the operational technology (OT) environment to detect unpatched instances proactively.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
VulnCheck
Date Reserved
2025-04-15T19:15:22.574Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68dfee6e88368ae77cfd5805

Added to database: 10/3/2025, 3:40:30 PM

Last enriched: 11/13/2025, 11:12:37 PM

Last updated: 11/18/2025, 6:21:06 AM

Views: 123

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats