Skip to main content
VulnerabilityPublished Updated

CVE-2025-0162: IBM Aspera Shares · XML External Entity (XXE)

Affects IBM Aspera SharesSource CVE Database V5

0

Not known to be exploited · CVSS 7.1 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Mar 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
IBM Aspera SharesAffected
  • =1.9.9
Fixed in–

AI-suggested

To mitigate CVE-2025-0162 effectively, European organizations should implement the following specific measures: 1) Restrict and monitor access to IBM Aspera Shares instances, ensuring that only authorized users with a legitimate need have authentication credentials. 2) Employ network segmentation and firewall rules to limit exposure of Aspera Shares servers to trusted networks and users. 3) Enable and review detailed logging and alerting on XML processing errors and unusual memory usage patterns to detect potential exploitation attempts early. 4) Apply strict input validation and sanitization on XML data where possible, or configure XML parsers to disable external entity processing if configurable. 5) Conduct regular credential audits and enforce strong authentication mechanisms, such as multi-factor authentication, to reduce the risk of credential compromise. 6) Prepare incident response plans specifically addressing XXE attack scenarios. 7) Monitor IBM security advisories closely for patches or updates and plan for rapid deployment once available. 8) Consider temporary alternative secure file transfer solutions if risk exposure is unacceptable until a patch is released.

Description

IBM Aspera Shares 1.9.9 through 1.10.0 PL7 is vulnerable to an XML external entity injection (XXE) attack when processing XML data. A remote authenticated attacker could exploit this vulnerability to expose sensitive information or consume memory resources.

References

Community reviews

Loading reviews…