How severe is CVE-2026-11980?

CVE-2026-11980 has a CVSS 3.x base score of 7.3, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2026-11980 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (7th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-11980?

CVE-2026-11980 affects Ibm Aspera. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-11980?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2026-11980 published?

CVE-2026-11980 was published on 2026-07-30 and last updated on 2026-08-13.

CVE-2026-11980

CVE-2026-11980 is a high-severity vulnerability in Ibm Aspera with a CVSS 3.x base score of 7.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-242.

Key facts

Severity: High (CVSS 3.x base score 7.3)
EPSS exploit prediction: 0% (7th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-242
Affected product: Ibm Aspera
Published: 2026-07-30
Last modified: 2026-08-13

Description

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

Frequently asked questions

What is CVE-2026-11980?: IBM Aspera Desktop App 1.0.5 through 1.0.19 can allow arbitrary code execution by loading DLL files at start-up.
How severe is CVE-2026-11980?: CVE-2026-11980 has a CVSS 3.x base score of 7.3, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-11980 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (7th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-11980?: CVE-2026-11980 affects Ibm Aspera. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-11980?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2026-11980 published?: CVE-2026-11980 was published on 2026-07-30 and last updated on 2026-08-13.

References

https://www.ibm.com/support/pages/node/7280939

Affected products (1)

cpe:2.3:a:ibm:aspera:*:*:*:*:desktop:*:*:*

More vulnerabilities in Ibm Aspera

CVE-2026-14973 — Critical (CVSS 9.3): IBM Aspera Desktop App 1.0.5 through 1.0.19 IBM Aspera for desktop can allow files to be written outside of the user's…

All CVEs affecting Ibm Aspera →

Other CWE-242 vulnerabilities

CVE-2024-52324 — Critical (CVSS 9.8): Ruijie Reyee OS versions 2.206.x up to but not including 2.320.x uses an inherently dangerous function which could…
CVE-2026-6477 — High (CVSS 8.8): Use of inherently dangerous function PQfn(..., result_is_int=0, ...) in PostgreSQL libpq lo_export(), lo_read(),…
CVE-2022-36310 — High (CVSS 8.8): Airspan AirVelocity 1500 software prior to version 15.18.00.2511 had NET-SNMP-EXTEND-MIB enabled on its snmpd service,…
CVE-2025-1994 — High (CVSS 7.8): IBM Cognos Command Center 10.2.4.1 and 10.2.5 could allow a local user to execute arbitrary code on the system due…
CVE-2025-1331 — High (CVSS 7.8): IBM CICS TX Standard 11.1 and IBM CICS TX Advanced 10.1 and 11.1 could allow a local user to execute arbitrary code on…
CVE-2021-42543 — High (CVSS 7.8): The affected application uses specific functions that could be abused through a crafted project file, which could lead…

Browse all CWE-242 vulnerabilities →