# CVE-2025-13213: Multiple vulnerabilities in IBM Aspera Orchestrator

> Attackers can inject HTTP headers to perform cross-site scripting, cache poisoning, or session hijacking on IBM Aspera Orchestrator.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Mar 2026
- **Updated:** 11 Mar 2026
- **Also known as:** GHSA-3v4c-g5c7-652p

## What is CVE-2025-13213?

CVE-2025-13213 is a medium-severity cross-site scripting vulnerability in IBM Aspera Orchestrator, published on 10 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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

Weakness: CWE-644 (Improper Neutralization of HTTP Headers for Scripting Syntax)

## Which versions are affected by CVE-2025-13213?

It affects 1 product.


Products: Ibm Aspera Orchestrator.

## How do I fix CVE-2025-13213?

No fix has been published for CVE-2025-13213 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-13213 being exploited?

There is no known exploitation of CVE-2025-13213 in the wild and no public exploit code.

## Other vulnerabilities in IBM Aspera Orchestrator

- [CVE-2025-13481](https://insights.sbomify.com/CVE-2025-13481/): IBM Aspera Orchestrator Command Injection (high 8.8)
- [CVE-2023-37407](https://insights.sbomify.com/CVE-2023-37407/): IBM Aspera Orchestrator command execution (high 8.8)
- [CVE-2025-13148](https://insights.sbomify.com/CVE-2025-13148/): IBM Aspera Orchestrator Unverified Password Change (high 8.1)
- [CVE-2025-13214](https://insights.sbomify.com/CVE-2025-13214/): IBM Aspera Orchestrator SQL Injection (high 7.6)
- [CVE-2023-38001](https://insights.sbomify.com/CVE-2023-38001/): IBM Aspera Orchestrator cross-site request forgery (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-13213 and fix it if it is affected.

What it is: CVE-2025-13213 is a medium-severity cross-site scripting vulnerability in IBM Aspera Orchestrator, published on 10 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-13213 in the wild and no public exploit code.

Affected product: IBM Aspera Orchestrator. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-13213/ (Markdown: https://insights.sbomify.com/CVE-2025-13213/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-13213
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-13213
- OSV: https://osv.dev/vulnerability/CVE-2025-13213

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-13213/
Summaries are generated and may contain mistakes; the official description above is the record.