Cyber Resilience

CVE-2026-11980

Ibm Aspera Desktop App 1.0.5 – 1.0.19

Published
30 July 2026
Modified
12 August 2026
Patch / advisory
View advisory
CVSS Score v3.1 7.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.0017 7th percentile
Risk Priority 51 floored blend · peak EPSS

Summary

CVE-2026-11980 is a high-severity Use of Inherently Dangerous Function (CWE-242) vulnerability in Ibm Aspera Desktop App. Its CVSS base score is 7.3 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 7th 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 SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

IBM Aspera Desktop App 1.0.5 through 1.0.19 can allow arbitrary code execution by loading DLL files at start-up.

CWE(s)
CWE-242

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-1331Same product: Linux Linux Kernel
CVE-2023-43799Same product: Apple Macos
CVE-2024-1882Same product: Apple Macos
CVE-2025-1095Same product: Apple Macos
CVE-2025-27906Same product: Apple Macos
CVE-2023-26512Same product: Apple Macos
CVE-2025-33126Same product: Linux Linux Kernel
CVE-2026-8835Same product: Linux Linux Kernel
CVE-2026-8834Same product: Linux Linux Kernel
CVE-2025-33132Same product: Linux Linux Kernel

Affected Assets

ibm
aspera desktop app
1.0.5 — 1.0.19

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and code analysis can locate calls to known dangerous functions after they have been written.

SA-15 Development Process, Standards, and Tools partial match

Documented development standards and tools can explicitly prohibit or replace inherently dangerous functions.

SA-3 System Development Life Cycle partial match

An SDLC that incorporates security can embed rules against unsafe functions in coding and review phases.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles can mandate avoidance of unsafe library functions during design and coding.

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.PS-06 mostly match
prevents

Secure SDLC practices directly prohibit or replace inherently dangerous functions via coding standards, reviews, and tooling.

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.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can surface calls to unsafe functions but does not prevent their introduction.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC processes include code review and static analysis that can detect dangerous function usage.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly ban or restrict inherently dangerous functions.

A.8.19 Installation of software on operational systems none match
none

Controlled software installation reduces exposure to unsafe third-party code containing dangerous functions.

References