VulnerabilityPublished 4 Nov 2025Updated 5 Nov 2025

CVE-2025-35021: Abilis CPX · Insecure Default Initialization of Resource

Affects Abilis CPXSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 09:08 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Abilis CPX	Affected =0	Fixed in–

AI-suggested

1. Ensure all Abilis CPX devices are fully configured and hardened before deployment; never expose unconfigured devices on production networks. 2. Implement strict network segmentation and access control lists (ACLs) to restrict SSH access to trusted management hosts only. 3. Monitor SSH login attempts and alert on repeated failed authentications followed by successful access to restricted shells. 4. Use out-of-band management networks for device provisioning to isolate unconfigured devices from general network traffic. 5. Regularly audit device configurations and reset procedures to prevent accidental exposure of unconfigured devices. 6. Engage with Abilis for firmware updates or patches once available and apply them promptly. 7. Incorporate device initialization checks into security policies and incident response plans to detect and respond to exploitation attempts. 8. Educate network administrators on the risks of default device states and enforce strict operational procedures during device setup.

Description

By failing to authenticate three times to an unconfigured Abilis CPX device via SSH, an attacker can login to a restricted shell on the fourth attempt, and from there, relay connections.

Impact

For European organizations, this vulnerability could lead to unauthorized access to network devices during initial deployment or after resets, potentially allowing attackers to relay traffic and gain footholds within internal networks. This can compromise confidentiality and integrity of data passing through or managed by the device. Critical infrastructure providers, telecom operators, and enterprises using Abilis CPX for secure connectivity may face increased risk of lateral movement attacks or data interception. The lack of authentication on unconfigured devices means attackers with network access can exploit this vulnerability remotely without user interaction. While availability is not directly impacted, the indirect effects of unauthorized access could lead to broader security incidents. The vulnerability is particularly concerning in environments with weak network segmentation or insufficient monitoring of device provisioning processes. European organizations must consider the risk to supply chain security and device lifecycle management to prevent exploitation.

CWE-1188Initialization of a Resource with an Insecure Default (opens in a new tab)
Base weakness
The product initializes or sets a resource with a default that is intended to be changed by the product's installer, administrator, or maintainer, but the default is not secure.
OWASP Cheat Sheets
Forgot Password (opens in a new tab)
OWASP ASVS 4.0.3
V2.3.1 (opens in a new tab)
V2.6.2 (opens in a new tab)
V2.7.6 (opens in a new tab)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Nov 2025, 05:36 UTC

WeaknessesCWE-1188

Technical details

References

Community reviews

Related threats