🛡️ CVE-2026-11980 — aspera

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. A user must be tricked into taking some action. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity high, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

• Attack vector: Local — a local account, shell or session on the host is needed.
• Attack complexity: Low — the attack works reliably, with no preparation.
• Privileges required: Low — an ordinary user account is enough.
• User interaction: Required — someone has to click, open or visit something.
• Scope: Unchanged — the damage stays inside the vulnerable component.
• Confidentiality impact: High — total loss, or loss the attacker controls.
• Integrity impact: High — total loss, or loss the attacker controls.
• Availability impact: High — total loss, or loss the attacker controls.

Weakness class

CVE-2026-11980 is classified as CWE-242: Use of Inherently Dangerous Function. The product calls a function that can never be guaranteed to work safely.

Affected software

CVE-2026-11980 is recorded against 1 package.

• aspera (from 1.0.5 up to 1.0.19)

Timeline and source

Published on 30 July 2026 and last revised on 13 August 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.

References

www.ibm.com

Other advisories for this package

aspera has other advisories on record. If you are patching this one, these are worth checking on the same host:

• CVE-2026-14973 (9.3 Critical, published 28 Jul 2026)

Same weakness in other software

These advisories are the same class of weakness (CWE-242: Use of Inherently Dangerous Function) in other software:

• CVE-2026-6477 (8.0 High, published 18 May 2026)
• CVE-2025-1994 (7.8 High, published 26 Aug 2025)
• CVE-2025-49215 (8.8 High, published 17 Jun 2025)
• CVE-2025-1331 (7.8 High, published 8 May 2025)
• CVE-2024-52324 (9.8 Critical, published 6 Dec 2024)
• CVE-2022-36310 (8.8 High, published 16 Aug 2022)

Details

Affected Packages

References