Skip to main content
CVE-2025-36171VulnerabilityPublished

CVE-2025-36171: IBM Aspera Faspex · Unthrottled Resource Allocation

Affects IBM Aspera FaspexSource CVE Database V5

0

Not known to be exploited · CVSS 4.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
4.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 24% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
IBM Aspera FaspexAffected
  • =5.0.0
Fixed in–

AI-suggested

European organizations should implement strict privilege management policies to limit access to IBM Aspera Faspex administrative functions and APIs. Monitoring and alerting on unusual resource consumption patterns within Faspex can help detect early signs of exploitation attempts. Network segmentation and access controls should be enforced to restrict API access to trusted administrators only. Until IBM releases an official patch, organizations can consider implementing resource usage limits at the operating system or container level to prevent excessive consumption by Faspex processes. Regularly reviewing and updating security configurations and conducting internal audits of privileged user activities will reduce the risk of insider exploitation. Additionally, organizations should maintain up-to-date backups and incident response plans to quickly recover from potential DoS incidents. Close coordination with IBM support and monitoring IBM security advisories for patch releases is essential for timely remediation.

Description

IBM Aspera Faspex 5.0.0 through 5.0.13.1 could allow a privileged user to cause a denial of service from improperly validated API input due to excessive resource consumption.

References

Community reviews

Loading reviews…