dbcve.org
Aspera FaspexApplication · Ibm

CVE-2025-33136

HIGH · 8.8 CVSS v3.1 Published 2025-05-22
Fix available
A fix is available. Upgrade to 5.0.12.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

IBM Aspera Faspex versions 5.0.0-5.0.12 contains an access control vulnerability where authenticated users can perform unauthorized actions or access sensitive information belonging to other users. The root cause is improper protection of data assumed to be immutable (likely user identifiers, session data, or object references), allowing attackers to manipulate these values to access resources of other users.

MitigationUpgrade to IBM Aspera Faspex version 5.0.13 or later. If immediate patching is not possible, implement strict validation of all user identifiers and object references server-side, and audit access control logic for all privileged operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Aspera FaspexApplication
Affected:>= 5.0.0, < 5.0.12.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed IBM Aspera Faspex version
    Locate the Faspex application and retrieve its version number. This is typically available via the web interface login page, admin console, or by checking application files such as VERSION, package.json, or the installation directory metadata. Use commands like 'rpm -qa | grep aspera' or 'ls -la /opt/aspera/faspex' if installed on Linux.
    Affected if The version is 5.0.0 through 5.0.12 (any version >= 5.0.0 but < 5.0.12.1)
  2. Verify product is exposed on network
    Determine if the IBM Aspera Faspex web interface or API is accessible from the network. Check firewall rules, reverse proxy configurations, or perform a port scan for typical Faspex ports (default HTTPS port 443 or custom).
    Affected if The Faspex web interface is network-accessible to users or systems outside the trusted administrative boundary
  3. Confirm authentication is enabled
    Review the Faspex authentication configuration to confirm that user authentication is required for access. Check whether guest access, anonymous access, or token-based API access is permitted without full authentication.
    Affected if Non-admin or untrusted users can authenticate to the system (which enables the exploitation pathway)
  4. Check for recent access logs indicating cross-user resource access
    Review Faspex server access logs, audit logs, or security event logs for patterns where user identifiers or object references appear to be manipulated. Look for repeated requests with sequential user IDs or abnormal access patterns to other users packages/transfers.
    Affected if Logs show evidence of unauthorized cross-user access or suspicious parameter manipulation

You are affected if IBM Aspera Faspex version 5.0.0 through 5.0.12 is installed and accessible, with user authentication enabled that allows untrusted users to interact with the application.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.0.12.1 or later
Fixed in 5.0.12.1
Interim mitigation

Upgrade to IBM Aspera Faspex version 5.0.13 or later. If immediate patching is not possible, implement strict validation of all user identifiers and object references server-side, and audit access control logic for all privileged operations.

Recommended fix High confidence

5.0.12.1

  1. Back up the current Aspera Faspex installation, configuration, and database before upgrading.
  2. Download Aspera Faspex version 5.0.12.1 from the official IBM/Aspera download portal or support site.
  3. Stop the Aspera Faspex service to ensure no active sessions during upgrade.
  4. Install the version 5.0.12.1 upgrade using the standard Aspera installation process (refer to IBM documentation for your platform).
  5. Verify the upgrade was successful by checking the installed version matches 5.0.12.1.
  6. Start the Aspera Faspex service and verify all components are running correctly.
  7. Log in and verify normal functionality works as expected.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Aspera Faspex Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-33136 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-33136 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data