VulnerabilityPublished 13 Mar 2026Updated 16 Mar 2026

CVE-2025-13459: IBM Aspera Console · Improper Enforcement of Behavioral Workflow

Affects IBM Aspera ConsoleSource CVE Database V5

Compare

Not known to be exploited · CVSS 2.7 Low.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

2.7Low

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

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

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

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

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: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
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: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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
IBMAspera Console	Affected >=3.3.0 <=3.4.8	Fixed in–

CPE configurations (2)

cpe:2.3:a:ibm:aspera_console:3.3.0:*:*:*:*:*:*:*
cpe:2.3:a:ibm:aspera_console:3.4.8:*:*:*:*:*:*:*

AI-suggested

To mitigate this vulnerability, organizations should: 1) Restrict and monitor privileged user access to IBM Aspera Console, ensuring only trusted administrators have high-level permissions. 2) Implement strict operational procedures and auditing to detect unusual or out-of-sequence workflow actions that could indicate exploitation attempts. 3) Apply patches or updates from IBM as soon as they become available to address the behavioral workflow enforcement issue. 4) Consider deploying redundant Aspera Console instances or failover mechanisms to maintain availability in case of denial of service. 5) Conduct regular security assessments and penetration testing focused on workflow enforcement and privilege misuse scenarios. 6) Educate administrators about the risks of improper workflow actions and the importance of following prescribed operational sequences. These steps go beyond generic advice by focusing on workflow integrity, privileged access controls, and operational continuity.

Description

IBM Aspera Console 3.3.0 through 3.4.8 could allow a privileged user to cause a denial of service due to improper enforcement of behavioral workflow.

Impact

The primary impact of this vulnerability is a denial of service condition that affects the availability of IBM Aspera Console. Organizations relying on Aspera Console for critical file transfer workflows could experience service interruptions, potentially delaying business processes and data transfers. Since the vulnerability requires privileged user access, the risk is mitigated by proper access controls; however, insider threats or compromised privileged accounts could exploit this flaw. The lack of impact on confidentiality and integrity reduces the risk of data breaches or unauthorized data manipulation. The low CVSS score and absence of known exploits suggest limited immediate threat, but denial of service in critical data transfer environments can still cause operational disruptions and financial losses. Organizations with large-scale or time-sensitive data transfer needs may face more significant consequences if the service becomes unavailable.

CWE-841Improper Enforcement of Behavioral Workflow (opens in a new tab)
Class weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product supports a session in which more than one behavior must be performed by an actor, but it does not properly ensure that the actor performs the behaviors in the required sequence or timeframe.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V11.1.1 (opens in a new tab)
V11.1.5 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

CPE configurations (2)

Description

AI analysisMachine-generated, updated 21 Mar 2026, 00:38 UTC

WeaknessesCWE-841

Technical details

References

Community reviews

Related threats