Skip to main content

IBM Aspera Orchestrator CVE-2025-13481

HIGH
OS Command Injection (CWE-78)
2025-12-11 psirt@us.ibm.com
8.8
CVSS 3.1 · Vendor: us
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain valid low-privilege credentials
  2. Delivery
    Authenticate to Aspera Orchestrator web interface
  3. Exploit
    Submit crafted input to vulnerable field
  4. Execution
    Trigger OS command injection (CWE-78)
  5. Persist
    Execute arbitrary commands with elevated privileges
  6. Impact
    Full host compromise

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization OS command sanitization, avoid shell exec
MITRE ATT&CK

2 techniques across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires an authenticated account on IBM Aspera Orchestrator (versions 4.0.0 through 4.1.0); the CVSS PR:L metric confirms some valid login is needed, so this is not exploitable by fully unauthenticated attackers. The flaw stems from improper validation of user-supplied input (CWE-78 OS command injection) in the application, which then executes commands at elevated privilege. Limiting factors: attacker must first possess or obtain valid credentials, and the instance must be reachable over the network (AV:N); no user interaction by a victim is required (UI:N) and attack complexity is low (AC:L). The provided data does not name the exact field, API, or configuration mode that carries the injection, so the specific vulnerable feature should be confirmed with the IBM advisory before scoping compensating controls.

Impact

Signals are moderately aligned but point to a credentialed-insider/post-compromise threat rather than mass internet exploitation. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 8.8 HIGH) describes network-reachable, low-complexity exploitation requiring low-level authentication (PR:L) with no user interaction and full CIA impact - consistent with a command-injection flaw (CWE-78) that lets an already-authenticated user escalate to arbitrary OS command execution with elevated privileges. However, EPSS is low at 0.48% (39th percentile), indicating no statistical evidence of imminent widespread exploitation, which is coherent with the PR:L authentication barrier. This is NOT in CISA KEV and no public exploit code was identified in the provided data, so there is no confirmed active exploitation. No SSVC decision data was supplied, so automatable/exploitation-maturity cannot be assessed from the input. Net: a genuine high-severity issue worth prioritized patching in environments running Aspera Orchestrator, but the authentication requirement and absence of KEV/POC signals place it below drop-everything internet-facing criticals - treat as high priority for exposed or multi-tenant deployments, standard patch cadence otherwise.

Exploit ScenarioDerived

An attacker who already holds valid low-privilege credentials to an IBM Aspera Orchestrator instance (4.0.0-4.1.0) submits crafted input into a field that is improperly validated, injecting OS commands that the application executes with elevated privileges. This yields arbitrary command execution on the underlying host, enabling full compromise of the Orchestrator server. No public exploit code was identified at time of analysis, and the attack requires authentication, so the realistic actor is a malicious insider or an attacker who has phished or otherwise obtained user credentials.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.5% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 07, 2026

Authenticated users of IBM Aspera Orchestrator 4.0.0 through 4.1.0 can inject operating-system commands that the application then executes with elevated privileges, giving a low-privileged account full control over the host (CVSS 3.1 base 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Because the CVSS vector carries PR:L, exploitation requires a valid login on the Orchestrator instance; the attacker does not need victim interaction and can reach the vulnerable component over the network, making this primarily a post-compromise or credentialed-insider escalation path rather than a mass internet-exploitation candidate. There is no CISA KEV listing and no public exploit identified at time of analysis, and EPSS is low at 0.48% (39th percentile), so immediate broad scanning activity is not indicated, but the impact once credentials are in hand is complete compromise of confidentiality, integrity, and availability.

RemediationAI

Consult the IBM advisory at https://www.ibm.com/support/pages/node/7254434 for the vendor-released fix level applicable to Aspera Orchestrator 4.0.0 through 4.1.0 and upgrade to that build; the supplied intelligence does not name an exact patched version, so no specific fix number should be assumed and the advisory must be treated as the source of truth. Until an upgrade is applied, reduce exposure by restricting network reachability of the Orchestrator interface to trusted management networks, VPN segments, or jump hosts rather than the general internet (trade-off: legitimate remote workflow and integration traffic from external networks must be re-routed through the same trusted path, which adds operational overhead). Enforce least privilege and strong authentication on all Orchestrator accounts, rotate credentials, remove stale or shared logins, and add MFA where the deployment supports it, since PR:L confirms a valid account is the entry condition (trade-off: tighter account controls can disrupt service accounts used for automated workflows, so they must be inventoried first). Also audit the host for unexpected child processes, shell invocations, or outbound connections originating from the Orchestrator service account, since command injection at elevated privilege may leave evidence only in process and command-line telemetry rather than in application logs.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-78, improper neutralization of special elements used in an OS command, arising from improper validation of user-supplied input in IBM Aspera Orchestrator. Aspera Orchestrator is a workflow orchestration layer used with Aspera high-speed transfer deployments, typically handling job definitions, process steps, and automation hooks that eventually invoke system-level operations; when a value derived from user input is passed unsanitized into such an invocation, an attacker who can reach that code path can append or substitute shell metacharacters and execute arbitrary commands. The CPE entry cpe:2.3:a:ibm:aspera_orchestrator:*:*:*:*:*:*:*:* is a wildcard covering the product family and does not itself enumerate versions, so the 4.0.0 through 4.1.0 range comes from the vendor description rather than the CPE. The assessed vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) confirms network reachability and low attack complexity but also confirms that some valid credential is a prerequisite (PR:L); the scope is unchanged (S:U), meaning the command execution is expected to remain within the vulnerable Orchestrator component's security authority, which includes the elevated privileges the service itself runs under. The provided data does not identify the exact field, API endpoint, or configuration mode that carries the injection, so the specific vulnerable feature should be confirmed against the IBM advisory before scoping compensating controls.

Know when Aspera Orchestrator gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (us) PRIMARY 8.8 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

Network-reachable app with low-complexity command injection; PR:L because a valid authenticated account is required; full host command execution gives C:H/I:H/A:H, scope unchanged.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (us).

CVSS VectorVendor: us

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

IBM Aspera Orchestrator versions 4.0.0 through 4.1.0 contain an operating-system command injection flaw that lets any user with a valid Orchestrator login run commands with elevated privileges, effectively handing over full control of the host. Organizations running these versions - particularly those with large user populations, shared service accounts, or third-party/contractor access to managed file transfer workflows - should treat this as a credential-compromise escalation risk rather than an internet-facing mass-exploitation event. Leadership should care because a single compromised or malicious low-privilege account can escalate to complete loss of confidentiality, integrity, and availability of the Orchestrator server and the file-transfer operations it governs.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: restrict and segment network access to the Orchestrator interface, enforce VPN/allow-listing for administrative access, aggressively minimize and monitor authenticated accounts (especially shared or service accounts), apply least-privilege and service-account hardening to prevent shell or interpreter invocation, rotate credentials for all Orchestrator and integrated accounts, and enable process-execution logging and alerting to detect post-exploitation command injection. There is no public exploit identified at time of analysis, so risk is currently concentrated in credentialed-insider and post-compromise scenarios.

Threat Intelligence Overview

EPSS Score
0.5%
Top 61% exploitable
Prevalence
Low
specialized IBM enterprise file-transfer workflow product, niche deployment
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.5%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

OS command injection occurs when an application passes unsanitized user input directly into system shell commands.

Affected Products (CPE)CVE.org

cpe:2.3:a:ibm:aspera_orchestrator:*:*:*:*:*:*:*:*

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy