dbcve.org
Aspera High Speed Transfer EndpointApplication · Ibm

CVE-2026-9035

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-27
Fix available
A fix is available. Upgrade to after 4.4.6 or later.
See remediation →
71/100
Remediation priority · Elevated
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 High-Speed Transfer Endpoint 3.7.4 through 4.4.7 Fix Pack 1 and IBM Aspera High-Speed Transfer Server 3.7.4 through 4.4.7 Fix Pack 1 and IBM Aspera High-Speed Transfer Endpoint are affected by a potential arbitrary file read in the asperahttpd component. An authenticated user may be able to take advantage of this vulnerability to access files in the server’s local storage that they should not have access to.

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 · high confidence

The vulnerability exists in the asperahttpd component of IBM Aspera High-Speed Transfer products. An authenticated user can exploit improper access controls to read arbitrary files on the server's local storage that should be restricted, potentially exposing sensitive system files or configuration data.

MitigationApply the vendor patch or upgrade to a version beyond 4.4.7 Fix Pack 1. If immediate patching is not feasible, restrict asperahttpd component access to only necessary authenticated users and monitor for unauthorized file access attempts.

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 High Speed Transfer EndpointApplication
Affected:>= 3.7.4, <= 4.4.6= 4.4.7
Aspera High Speed Transfer ServerApplication
Affected:>= 3.7.4, <= 4.4.6= 4.4.7

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
None
Availability
None

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

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 Aspera product
    Run 'ibm-aspera-hsts --version' or check installed packages via package manager (rpm -qa | grep aspera or dpkg -l | grep aspera)
    Affected if Product is IBM Aspera High-Speed Transfer Endpoint or Server
  2. Determine asperahttpd component version
    Run 'asperahttpd --version' or check the version of the asperahttpd package specifically
    Affected if Version is 3.7.4 through 4.4.6 inclusive, or exactly 4.4.7
  3. Verify asperahttpd service is running
    Check process list with 'ps aux | grep asperahttpd' or check service status via 'systemctl status asperahttpd'
    Affected if asperahttpd service is active and exposed to network
  4. Check asperahttpd configuration for access controls
    Inspect asperahttpd.conf or common config locations under /opt/aspera/etc/ for permission settings and user restrictions
    Affected if No strict user restrictions configured or authentication bypass is possible
  5. Test for unauthorized file access (if safe to do)
    As an authenticated user, attempt to access a restricted file path via asperahttpd API endpoint to confirm the vulnerability exists
    Affected if Able to read files outside allowed directories

Your environment is affected if you run asperahttpd version 3.7.4 through 4.4.7 on IBM Aspera High-Speed Transfer products, and the component is accessible to authenticated users without proper restrictions.

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 a release after 4.4.6
Interim mitigation

Apply the vendor patch or upgrade to a version beyond 4.4.7 Fix Pack 1. If immediate patching is not feasible, restrict asperahttpd component access to only necessary authenticated users and monitor for unauthorized file access attempts.

Recommended fix Moderate confidence

Upgrade to the latest available Aspera release beyond 4.4.7 Fix Pack 1 (check IBM Fix Central for the most current fixed version)

  1. 1. Identify the currently installed Aspera High-Speed Transfer Endpoint or Server version using the aspera version command or admin console
  2. 2. Confirm the installed version falls within the affected range: 3.7.4 through 4.4.7 (including Fix Pack 1)
  3. 3. Schedule a maintenance window for the upgrade process
  4. 4. Back up all configuration files, transfer data, and database (if applicable) before proceeding
  5. 5. Download the latest Aspera release from IBM Fix Central (https://www.ibm.com/support/fixcentral) or the Aspera downloads portal
  6. 6. Install the upgrade following the Aspera installation guide for your platform (Linux or Windows)
  7. 7. After upgrade, verify the asperahttpd service is running and the new version is reflected in the admin console
  8. 8. Test file transfer functionality to confirm normal operations
Caveat Review IBM Aspera release notes for any configuration or feature changes between your current version and the target version; some settings may require adjustment

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

Fix this in Aspera High Speed Transfer Endpoint Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9035 — 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-2026-9035 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