Skip to main content
VulnerabilityPublished

CVE-2025-13213: IBM Aspera Orchestrator · Improper Neutralization of HTTP Headers for Scripting Syntax

Affects IBM Aspera OrchestratorSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.4 Medium.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 7% 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:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Mar 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 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
IBMAspera OrchestratorAffected
  • >=3.0.0 <=4.1.2
Fixed in–

CPE configurations (2)

  • cpe:2.3:a:ibm:aspera_orchestrator:3.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:aspera_orchestrator:4.1.2:*:*:*:*:*:*:*

AI-suggested

  1. Implement strict validation and sanitization of HTTP HOST headers at the application or web server level to reject malformed or suspicious inputs.
  2. Deploy Web Application Firewalls (WAFs) with custom rules to detect and block HTTP header injection attempts targeting HOST headers.
  3. Restrict network access to IBM Aspera Orchestrator interfaces to trusted internal networks or VPNs, minimizing exposure to untrusted sources.
  4. Monitor HTTP traffic logs for unusual or anomalous HOST header values that could indicate exploitation attempts.
  5. Apply network segmentation to isolate Aspera Orchestrator servers from general user networks and limit lateral movement.
  6. Stay alert for IBM security advisories and apply official patches or updates promptly once released.
  7. Educate administrators and users about the risks of XSS and session hijacking to recognize suspicious behavior.
  8. Consider implementing Content Security Policy (CSP) headers to mitigate impact of potential XSS attacks.
  9. Conduct regular security assessments and penetration tests focusing on HTTP header injection vectors.

Description

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 or session hijacking

References

Community reviews

Loading reviews…