Skip to main content
VulnerabilityPublished

CVE-2025-13481: IBM Aspera Orchestrator · OS Command Injection

Affects IBM Aspera OrchestratorSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 41% 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:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Dec 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 OrchestratorAffected
  • =4.0.0
Fixed in–

AI-suggested

  1. Immediately restrict access to IBM Aspera Orchestrator interfaces to trusted and authenticated users only, ideally limiting network exposure via firewalls or VPNs.
  2. Implement strict input validation and sanitization on all user-supplied data to prevent injection of special characters or commands.
  3. Monitor system and application logs for unusual command execution patterns or privilege escalations.
  4. Apply the official IBM patches or updates as soon as they become available; if patches are not yet released, consider temporary workarounds such as disabling vulnerable features or running the service with minimal privileges.
  5. Conduct thorough security audits and penetration testing focused on command injection vectors within the orchestration environment.
  6. Educate administrators and users on the risks of command injection and enforce the principle of least privilege for all accounts interacting with Aspera Orchestrator.
  7. Employ endpoint detection and response (EDR) solutions to detect and respond to suspicious activities related to command execution.
  8. Maintain up-to-date backups and incident response plans to quickly recover from potential compromises.

Description

IBM Aspera Orchestrator 4.0.0 through 4.1.0 could allow an authenticated user to execute arbitrary commands with elevated privileges on the system due to improper validation of user supplied input.

References

Community reviews

Loading reviews…