Communication outage via unbounded interface resource allocation
Published Aug 12, 2026 · Updated Aug 12, 2026
Resource exhaustion in PLCnext firmware before 2026.0.3 allows remote attackers to interrupt PLCnext Engineer communication. The PLCnext Engineer communication interface allocates resources without limits or throttling, although the published advisory does not identify the specific resource or request sequence. No authentication or user interaction is required, and successful exploitation blocks client access until the PLCnext service is manually restarted.
Summary
What happened
Resource exhaustion in PLCnext firmware before 2026.0.3 allows remote attackers to interrupt PLCnext Engineer communication. The PLCnext Engineer communication interface allocates resources without limits or throttling, although the published advisory does not identify the specific resource or request sequence. No authentication or user interaction is required, and successful exploitation blocks client access until the PLCnext service is manually restarted.
The record
- CVE
- CVE-2025-41770
- Published
- Aug 12, 2026
- Updated
- Aug 12, 2026
- Vendor
- Phoenix Contact
- Product
- BPC 9102S
- Classifications
- CWE-770, CAPEC-130, T0814
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 12, 2026CVE publishedPublication date reported by the CVE source.
- Aug 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2019.0.4 <2026.0.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo