dbcve.org
Aspera SharesApplication · Ibm

CVE-2025-13916

HIGH · 7.5 CVSS v3.1 Published 2026-04-01
Fix available
A fix is available. Upgrade to 1.11.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 Shares 1.9.9 through 1.11.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information

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 Shares versions 1.9.9 through 1.11.0 implements weaker than expected cryptographic algorithms (e.g., weak ciphers, improper key derivation, or deprecated protocols), allowing an attacker with network access to decrypt highly sensitive data stored or transmitted through the platform.

MitigationUpgrade IBM Aspera Shares to version 1.11.1 or later which implements stronger cryptographic algorithms; if immediate upgrade is not possible, identify and disable weak cipher suites in the configuration and ensure TLS 1.2+ with strong ciphers is enforced for all communications.

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 SharesApplication
Affected:>= 1.9.9, < 1.11.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 the installed IBM Aspera Shares version
    Locate the version information in the product installation directory, admin console, or by running the product version command. Common locations include /opt/aspera/shares/version or the web admin interface.
    Affected if The installed version is 1.9.9, 1.10.0, or 1.11.0 (any version >= 1.9.9 and < 1.11.1)
  2. Review TLS configuration for weak cipher suites
    Access the Aspera Shares configuration files or admin panel and examine the enabled cipher suites. Look for cipher suites using MD5, SHA-1, or 3DES, or those with key lengths below 128 bits.
    Affected if Weak cipher suites such as those using MD5, SHA-1, or short key lengths (below 128-bit) are enabled
  3. Verify TLS protocol version settings
    Check the TLS settings in the Aspera Shares configuration to determine which protocol versions are enabled. Inspect the server configuration or SSL/TLS settings files.
    Affected if TLS 1.0 or TLS 1.1 (deprecated protocols) are enabled instead of requiring TLS 1.2 or higher
  4. Inspect key derivation and encryption settings
    Examine the cryptographic configuration files or admin settings related to data encryption, key exchange, and key derivation methods used for stored or transmitted data.
    Affected if Weak or deprecated key derivation functions (such as MD5-based or SHA-1-based) are in use

A user is affected if their IBM Aspera Shares version is between 1.9.9 and 1.11.0 inclusive, or if weak ciphers, deprecated TLS protocols, or improper key derivation are configured.

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 1.11.1 or later
Fixed in 1.11.1
Interim mitigation

Upgrade IBM Aspera Shares to version 1.11.1 or later which implements stronger cryptographic algorithms; if immediate upgrade is not possible, identify and disable weak cipher suites in the configuration and ensure TLS 1.2+ with strong ciphers is enforced for all communications.

Recommended fix High confidence

IBM Aspera Shares 1.11.1 or later

  1. 1. Create a complete backup of the current Aspera Shares installation including database and configuration files
  2. 2. Download IBM Aspera Shares version 1.11.1 or later from the official IBM Aspera website or authorized distribution channel
  3. 3. Review IBM Aspera Shares upgrade documentation for version 1.11.1
  4. 4. Stop the Aspera Shares service before applying the upgrade
  5. 5. Apply the upgrade to version 1.11.1 following IBM's standard upgrade procedure
  6. 6. Start the Aspera Shares service after upgrade completion
  7. 7. Verify the upgrade was successful by checking the version number in the admin interface
  8. 8. Test critical functionality including file transfers and authentication to ensure proper operation
Caveat Review IBM release notes for version 1.11.1 to check for any configuration or feature changes that may require adjustment

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

Fix this in Aspera Shares Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
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,776.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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