AXC F 1152: Allocation of Resources Without Limits or Throttling
CVE-2025-41770 is a high-severity allocation of resources without limits or throttling vulnerability in AXC F 1152 from Phoenix Contact, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 2026.0.3 as the first without the flaw, so updating AXC F 1152 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.55% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update AXC F 1152 to 2026.0.3 or a later version.
- Update AXC F 1252 to 2026.0.3 or a later version.
- Update AXC F 2000 EA to 2026.0.3 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Phoenix Contact | AXC F 1152 | 2019.0.4 up to, but not including, 2026.0.3 | 2026.0.3 |
| Phoenix Contact | AXC F 1252 | 2019.0.4 up to, but not including, 2026.0.3 | 2026.0.3 |
| Phoenix Contact | AXC F 2000 EA | 2019.0.4 up to, but not including, 2026.0.3 | 2026.0.3 |
| Phoenix Contact | AXC F 2152 | 2019.0.4 up to, but not including, 2026.0.3 | 2026.0.3 |
| Phoenix Contact | AXC F 3152 | 2019.0.4 up to, but not including, 2026.0.3 | 2026.0.3 |
| Phoenix Contact | BPC 9102S | 2019.0.4 up to, but not including, 2026.0.3 | 2026.0.3 |
| Phoenix Contact | BPC 9202S | 2019.0.4 up to, but not including, 2026.0.3 | 2026.0.3 |
| Phoenix Contact | RFC 4072R | 2019.0.4 up to, but not including, 2026.0.3 | 2026.0.3 |
| Phoenix Contact | RFC 4072S | 2019.0.4 up to, but not including, 2026.0.3 | 2026.0.3 |
| Phoenix Contact | VL3 UPC 2440 EDGE | 2019.0.4 up to, but not including, 2026.0.3 | 2026.0.3 |
| Phoenix Contact | VPLCNEXT CONTROL 1000 | 2019.0.4 up to, but not including, 2026.0.3 | 2026.0.3 |
| Phoenix Contact | VPLCNEXT CONTROL 2000 | 2019.0.4 up to, but not including, 2026.0.3 | 2026.0.3 |
| Phoenix Contact | VPLCNEXT CONTROL 3000 | 2019.0.4 up to, but not including, 2026.0.3 | 2026.0.3 |
| Phoenix Contact | VPLCNEXT CONTROL 500 | 2019.0.4 up to, but not including, 2026.0.3 | 2026.0.3 |
| Phoenix Contact | Catan C1 | 2019.0.4 up to, but not including, 2026.0.3 | 2026.0.3 |
| Phoenix Contact | EPC 1502 | 2019.0.4 up to, but not including, 2026.0.3 | 2026.0.3 |
| Phoenix Contact | EPC 1522 | 2019.0.4 up to, but not including, 2026.0.3 | 2026.0.3 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by CNA (cert.vde.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 8.7 | High | CNA (cert.vde.com) |
| CVSS 3.1 | 7.5 | High | CNA (cert.vde.com) |
Official description
An unauthenticated denial-of-service vulnerability in the device's PLCnext Engineer communication interface allow an remote attacker to interrupt access via the client application. Successful exploitation prevents communication until the PLCnext service is manually restarted.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Allocation of Resources Without Limits or Throttling
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
How developers prevent this class of flaw
- Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
- Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
More Allocation of Resources Without Limits or Throttling vulnerabilities (CWE-770)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in AXC F 1152
- 9.8 Critical severity
- 7.8 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
Recent Allocation of Resources Without Limits or Throttling vulnerabilities
- 8.7 High severity
- 7.5 High severity
- 7.5 High severity
- 9.9 Critical severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.