IBM Aspera Connect 1.6.1 through 4.2.19 could allow a remote attacker to obtain sensitive information and modify host
Source GCVE Database
Not known to be exploited · CVSS 6.4 Medium.
Data as of 8 Nov 2026, 20:48 UTC
Thin evidence
One scorer or none| CNA (ibm) | CVSS 3.1 | 6.4 |
|---|
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 8 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IBMAspera Connect | Affected
| Fixed in– |
AI-suggested
Until a fix is available, users should avoid visiting untrusted web pages while using affected versions and consider restricting access to the local HTTP service if possible.
Description
IBM Aspera Connect versions 1.6.1 through 4.2.19 have a vulnerability that allows remote attackers to obtain sensitive information and modify host trust configurations. This is due to missing authentication and overly permissive cross-origin resource sharing (CORS) policies in the local HTTP service. An attacker can exploit this by tricking a user into visiting a malicious web page, which then performs unauthorized cross-origin requests to read and alter configuration data.