Skip to main content
VulnerabilityPublished

CVE-2026-120115: IBM Aspera Connect 1.6.1 through 4.2.19 fails to consistently enforce origin verification across all

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-120115· Medium 6.3

Not known to be exploited · CVSS 6.3 Medium.

Data as of 8 Nov 2026, 20:50 UTC

CVSS 3.1 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (ibm)CVSS 3.16.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
IBMAspera ConnectAffected
  • >=1.6.1 <=4.2.19
Fixed in–

AI-suggested

Until a fix is available, users should exercise caution when interacting with untrusted websites and consider restricting access to the affected REST API endpoints if possible.

Description

IBM Aspera Connect versions 1.6.1 through 4.2.19 have a vulnerability where origin verification is not consistently enforced across all REST API endpoints. This flaw allows an attacker who tricks a user into visiting a malicious website to potentially delete or inspect the user's account configurations.

References

Community reviews

Loading reviews…