VulnerabilityPublished 26 Dec 2025

CVE-2025-36229: IBM Aspera Faspex 5 · Exposure of Sensitive System Information to an Unauthorized Control Sphere

Affects IBM Aspera Faspex 5Source CVE Database V5

Not known to be exploited · CVSS 3.1 Low.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score

3.1Low

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

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

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

Attack Vector: Network
Attack Complexity: High
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
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: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: None: There is no loss of integrity within 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 26 Dec 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 or the CVSS exploit maturity 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
IBM Aspera Faspex 5	Affected =5.0.0	Fixed in–

AI-suggested

To mitigate CVE-2025-36229, European organizations should implement the following specific measures: 1) Monitor IBM’s security advisories closely and apply patches or updates promptly once released to address this vulnerability. 2) Restrict authenticated user permissions within Faspex to the minimum necessary, employing the principle of least privilege to limit access to package enumeration functions. 3) Implement robust authentication mechanisms, including multi-factor authentication, to reduce the risk of unauthorized authenticated access. 4) Audit and monitor access logs for unusual enumeration patterns or repeated queries that may indicate exploitation attempts. 5) Segment the Faspex environment within the network to limit lateral movement opportunities for attackers who gain access. 6) Educate users and administrators about the risks of information enumeration and encourage reporting of suspicious activities. 7) Consider additional compensating controls such as network-level access restrictions and anomaly detection systems tailored to Faspex traffic patterns. These steps go beyond generic advice by focusing on access control hardening, proactive monitoring, and rapid patch management specific to the vulnerability context.

Description

IBM Aspera Faspex 5 5.0.0 through 5.0.14.1 could allow authenticated users to enumerate sensitive information of data due by enumerating package identifiers.

Impact

For European organizations, the primary impact of CVE-2025-36229 is the potential unauthorized disclosure of sensitive system information related to data package identifiers within IBM Aspera Faspex 5. This could lead to information leakage about data transfer activities, which may be leveraged for further reconnaissance or targeted attacks. Although the vulnerability does not allow data modification or service disruption, the exposure of metadata could compromise confidentiality, especially in sectors handling sensitive or regulated data such as finance, healthcare, and government. Organizations relying on Faspex for secure file transfers might face increased risks if attackers or malicious insiders exploit this flaw to map data flows or identify valuable data assets. However, the requirement for authenticated access and the high attack complexity reduce the likelihood of widespread exploitation. The absence of known exploits further limits immediate risk but does not eliminate the need for vigilance. Overall, the impact is moderate in confidentiality terms but low in terms of integrity and availability.

CWE-497Exposure of Sensitive System Information to an Unauthorized Control Sphere (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does.
Architecture and Design · Implementation
Production applications should never use methods that generate internal details such as stack traces and error messages unless that information is directly committed to a log that is not viewable by the end user.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V14.3.2 (opens in a new tab)
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
Attack patterns
Web Application Fingerprinting (opens in a new tab)
System Location Discovery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

ibm.com/support/pages/node/7255331 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Dec 2025, 14:44 UTC

WeaknessesCWE-497

Technical details

References

Community reviews

Related threats