Read the docs

Missing authentication and CORS flaws in IBM Aspera Connect

Priority LOW 29CWE-306Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
Required
Attack complexity
High
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · None
Fix status
No fix listed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-306.

Summary

IBM Aspera Connect from 1.6.1 through 4.2.19 lacks authentication on its local HTTP service (CWE-306), and overly permissive cross-origin access controls expose it to web pages. A remote attacker who persuades a victim to visit a malicious web page can read and modify configuration, including host trust settings.

Written with Claude Haiku 5.5 from the sources below · 2026-11-08

Description from the CNA

IBM Aspera Connect 1.6.1 through 4.2.19 could allow a remote attacker to obtain sensitive information and modify host trust configuration due to missing authentication and overly permissive cross-origin access controls in the local HTTP service. By persuading a victim to visit a malicious web page, an attacker could perform unauthorized cross-origin requests to read and modify configuration.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00367 31st percentileScored 2026-11-16
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
IBMAspera Connect1.6.1 – 4.2.19—No fix listedCNA
  • Aspera Connect VendorIBM Affected 1.6.1 – 4.2.19 Fixed in — No fix listed CNA

CPE names CNA · 2

CPEVersionsRoleVendor
cpe:2.3:a:ibm:aspera_connect:1.6.1:*:*:*:*:*:*:*1.6.1—IBM
cpe:2.3:a:ibm:aspera_connect:4.2.19:*:*:*:*:*:*:*4.2.19—IBM
  • cpe:2.3:a:ibm:aspera_connect:1.6.1:*:*:*:*:*:*:* Versions 1.6.1 — ·IBM
  • cpe:2.3:a:ibm:aspera_connect:4.2.19:*:*:*:*:*:*:* Versions 4.2.19 — ·IBM

Remediation

The sources list no fixed version for IBM Aspera Connect.

Written with Claude Haiku 5.5 from the sources below · 2026-11-08

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Advisory ·

    IBM Aspera Connect — ibm.com/support/pages/node/7295714

    2 records Highest priority Priority LOW 2 LOW

    Other records, highest priority first

    • TI-2026-86896 Missing origin verification in IBM Aspera Connect REST APIPriority LOW 28

Timeline

  1. 2026-11-08 Threatist record created from CVE-2026-120113
  2. 2026-11-08 Alias added: GHSA-78r2-chvp-r9hc
  3. 2026-11-10 Priority changed: MEDIUM → LOW
  4. 2026-11-12 CISA SSVC decision points changed

References

  • TI-2026-86195 IBM Aspera Faspex Authorization Bypass Allows Administrative Takeover KEVCVSS 3.1CRITICAL 9.8
  • TI-2026-08085 Unauthenticated code execution in IBM Langflow OSS KEVCVSS 3.1CRITICAL 9.8
  • TI-2022-23774 Code execution in IBM Aspera Faspex via YAML deserialization KEVCVSS 3.1CRITICAL 9.8
  • TI-2020-03794 Authentication bypass in IBM Data Risk Manager with SAML KEVCVSS 3.1CRITICAL 9.8
  • TI-2019-03441 IBM Planning Analytics configuration overwrite enables code execution KEVCVSS 3.1CRITICAL 9.8
  • TI-2017-03639 Command execution in Apache Struts 2 Jakarta Multipart parser KEVCVSS 3.1CRITICAL 9.8
See all 9818 →

Sources