Cyber Resilience

CVE-2025-33136

Ibm Aspera Faspex 5.0.0 – 5.0.12.1

Published
22 May 2025
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 7.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
EPSS Score 0.0031 24th percentile
Risk Priority 53 floored blend · peak EPSS

Summary

CVE-2025-33136 is a high-severity MAID (CWE-471) vulnerability in Ibm Aspera Faspex. Its CVSS base score is 7.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Path Interception (T1034); ranked at the 24th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1034 Path Interception Persistence
**This technique has been deprecated.
T1547 Boot or Logon Autostart Execution Persistence
Adversaries may configure system settings to automatically execute a program during system boot or logon to maintain persistence or gain higher-level privileges on compromised systems.
T1574 Hijack Execution Flow Stealth
Adversaries may execute their own malicious payloads by hijacking the way operating systems run programs.
T1546 Event Triggered Execution Privilege Escalation
Adversaries may establish persistence and/or elevate privileges using system mechanisms that trigger execution based on specific events.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-14958Same product: Ibm Aspera Faspex
CVE-2023-27871Same product: Ibm Aspera Faspex
CVE-2025-36226Same product: Ibm Aspera Faspex
CVE-2025-36227Same product: Ibm Aspera Faspex
CVE-2025-33137Same product: Ibm Aspera Faspex
CVE-2023-35906Same product: Ibm Aspera Faspex
CVE-2023-27874Same product: Ibm Aspera Faspex
CVE-2023-24965Same product: Ibm Aspera Faspex
CVE-2025-3423Same product: Ibm Aspera Faspex
CVE-2023-22870Same product: Ibm Aspera Faspex

Affected Assets

ibm
aspera faspex
5.0.0 — 5.0.12.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 1 hardening rule · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

Access enforcement directly stops unauthorized modification of elements that should remain immutable.

Least privilege reduces the set of subjects that can reach or alter assumed-immutable data.

Integrity verification tools discover unauthorized changes after they occur.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-05 mostly match
prevents

Least-privilege access controls directly block unauthorized writes to assumed-immutable data.

PR.DS-01 mostly match
prevents

Integrity mechanisms for data-at-rest prevent modification of elements expected to remain immutable.

PR.DS-10 mostly match
prevents

Protecting data-in-use integrity stops runtime tampering of values treated as constant.

PR.IR-01 partial match
prevents

Logical access controls reduce the attack surface for modifying internal assumed-immutable state.

PR.PS-01 partial match
prevents

Hardened configuration baselines limit opportunities to alter data presumed immutable.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect unauthorized modification paths for assumed-immutable data.

prevents

Secure SDLC practices include design reviews that identify and protect data assumed to be immutable.

prevents

Application security requirements can mandate integrity protections for data declared immutable.

prevents

Secure architecture principles call for explicit immutability guarantees and enforcement mechanisms.

prevents

Secure coding standards discourage mutable storage for values that must remain constant.

mitigates

Access-control rules directly prevent unauthorized modification of data assumed to be immutable.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Windows 10 (1 rule)
  • V-220812 Credential Guard must be running on Windows 10 domain-joined systems. prevents CWE-471

References