VulnerabilityPublished 13 Mar 2026Updated 16 Mar 2026

CVE-2025-13212: IBM Aspera Console · Improper Control of Interaction Frequency

Affects IBM Aspera ConsoleSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.3 Medium.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score

5.3Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 20% 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:N/I:N/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
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: 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: 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 29 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 CVE-2025-13212, organizations should first verify if they are running affected versions of IBM Aspera Console (3.3.0 through 3.4.8) and prioritize upgrading to a patched version once available from IBM. In the absence of an immediate patch, administrators should implement strict access controls to limit authenticated user accounts to only those necessary, reducing the attack surface. Rate limiting or throttling mechanisms should be applied at the application or network level to restrict the frequency of email service interactions per user. Monitoring and alerting on unusual spikes in email service requests can help detect exploitation attempts early. Additionally, enforcing strong authentication methods and regularly auditing user activities can prevent misuse by compromised accounts. Network segmentation and firewall rules can restrict access to the console’s email service endpoints to trusted users and systems only. Engaging with IBM support for any recommended configuration changes or interim fixes is also advised.

Description

IBM Aspera Console 3.3.0 through 3.4.8 could allow an authenticated user to cause a denial of service in the email service due to improper control of interaction frequency.

Impact

The primary impact of CVE-2025-13212 is a denial of service condition affecting the email service within IBM Aspera Console. This can disrupt automated email notifications critical for operational awareness, alerting, and workflow management in organizations relying on Aspera Console for secure file transfers. The availability degradation could lead to delayed responses to important events, impacting business continuity and operational efficiency. Since the vulnerability requires authentication, the risk is somewhat mitigated by access controls, but insider threats or compromised credentials could still exploit this flaw. The vulnerability does not affect confidentiality or data integrity, so data breaches or unauthorized data modification are not concerns here. Organizations with high dependency on Aspera Console’s email notifications, especially in sectors like finance, healthcare, media, and government, may experience operational disruptions if exploited.

CWE-799Improper Control of Interaction Frequency (opens in a new tab)
Class weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product does not properly limit the number or frequency of interactions that it has with an actor, such as the number of incoming requests.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V11.1.2 (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-799

Technical details

References

Community reviews

Related threats