Cyber Resilience

CVE-2025-13213

Ibm Aspera Orchestrator 3.0.0 – 4.1.3

Published
10 March 2026
Modified
12 March 2026
Patch / advisory
CVSS Score v3.1 5.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
EPSS Score 0.0016 6th percentile
Risk Priority 41 floored blend · peak EPSS

Summary

CVE-2025-13213 is a medium-severity Improper Neutralization of HTTP Headers for Scripting Syntax (CWE-644) vulnerability in Ibm Aspera Orchestrator. Its CVSS base score is 5.4 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 6th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

IBM Aspera Orchestrator 3.0.0 through 4.1.2 is vulnerable to HTTP header injection, caused by improper validation of input by the HOST headers. This could allow an attacker to conduct various attacks against the vulnerable system, including cross-site scripting, cache poisoning…

more

or session hijacking

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-36227Same product: Linux Linux Kernel
CVE-2025-0154Same product: Linux Linux Kernel
CVE-2025-13481Same product: Ibm Aspera Orchestrator
CVE-2025-13211Same product: Ibm Aspera Orchestrator
CVE-2025-13148Same product: Ibm Aspera Orchestrator
CVE-2025-13219Same product: Ibm Aspera Orchestrator
CVE-2025-13214Same product: Ibm Aspera Orchestrator
CVE-2025-14807Same product: Linux Linux Kernel
CVE-2024-40686Same vendor: Ibm
CVE-2024-51454Same vendor: Ibm

Affected Assets

ibm
aspera orchestrator
3.0.0 — 4.1.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V4.2.3

Mitigating Controls (NIST 800-53 r5) AI

Input validation directly requires checking/neutralizing untrusted data such as HTTP headers before they reach browser components.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper output encoding and header sanitization to prevent scripting injection.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing catches header-injection issues before release, covering most of the weakness.

prevents

Secure development lifecycle mandates input validation and output encoding that directly prevents header-injection flaws.

prevents

Application security requirements explicitly call for neutralizing untrusted data in HTTP headers.

prevents

Secure architecture principles reduce injection surfaces but do not prescribe header-specific controls.

prevents

Secure coding standards require proper escaping or rejection of scripting syntax in HTTP headers.

References