CVE-2025-33136

CVE-2025-33136 is a high-severity vulnerability in Ibm Aspera Faspex with a CVSS 3.x base score of 7.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-471.

Key facts

Description

IBM Aspera Faspex 5.0.0 through 5.0.12 could allow an authenticated user to obtain sensitive information or perform unauthorized actions on behalf of another user due to improper protection of assumed immutable data.

Frequently asked questions

What is CVE-2025-33136?
IBM Aspera Faspex 5.0.0 through 5.0.12 could allow an authenticated user to obtain sensitive information or perform unauthorized actions on behalf of another user due to improper protection of assumed immutable data.
How severe is CVE-2025-33136?
CVE-2025-33136 has a CVSS 3.x base score of 7.1, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity low, and availability none.
Is CVE-2025-33136 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (21st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-33136?
CVE-2025-33136 affects Ibm Aspera Faspex. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-33136?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-33136 have an EU (EUVD) identifier?
Yes. CVE-2025-33136 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-16173.
When was CVE-2025-33136 published?
CVE-2025-33136 was published on 2025-05-22 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Ibm Aspera Faspex

All CVEs affecting Ibm Aspera Faspex →

Other CWE-471 vulnerabilities

Browse all CWE-471 vulnerabilities →