CVE-2025-13219: IBM Aspera Orchestrator 3.0.0 through 4.1.2 stores sensitive information in URL parameters

Routine

MEDIUM 5.9REMOTEUPGRADE

CVE-2025-13219 is a medium-severity flaw (CVSS 5.9) affecting aspera orchestrator. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

IBM Aspera Orchestrator 3.0.0 through 4.1.2 stores sensitive information in URL parameters. This may lead to information disclosure if unauthorized parties have access to the URLs via server logs, referrer header or browser history.

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.9 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 71%)
CISA exploited list	No
Weakness	CWE-598
Published	2026-03-10
Last modified	2026-06-17

Publisher (CNA): IBM Corporation · Vendor: ibm

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-03-10 20:16 UTCPublished CVE record published
2026-06-17 08:33 UTCUpdated Record last modified

ibm aspera orchestrator UPGRADE

Affected: >= 3.0.0 and < 4.1.3

Fixed in: 4.1.3

Safe to downgrade to: a release before 3.0.0

1. Check installed version

apt-cache policy aspera-orchestrator || rpm -q aspera-orchestrator || aspera-orchestrator --version

2. UPGRADE to 4.1.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade aspera-orchestrator

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade aspera-orchestrator

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 3.0.0 (Debian / Ubuntu)

apt-cache madison aspera-orchestrator sudo apt install aspera-orchestrator=<VERSION_BEFORE_3.0.0> sudo apt-mark hold aspera-orchestrator

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list aspera-orchestrator sudo dnf downgrade aspera-orchestrator-<VERSION_BEFORE_3.0.0> sudo dnf versionlock add aspera-orchestrator

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-13219?

aspera orchestrator: upgrade to 4.1.3. Exact commands for each OS are on this page.

Is CVE-2025-13219 being exploited?

CVE-2025-13219 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-13219 affect?

CVE-2025-13219 affects aspera orchestrator. Severity is medium (CVSS 5.9). IBM Aspera Orchestrator 3.0.0 through 4.1.2 stores sensitive information in URL parameters. This may lead to information disclosure if unauthorized parties have access to the URLs via server logs, referrer header or browser history.

How urgent is CVE-2025-13219?

Priority 33/100. Remotely exploitable, no login, no user action

Related CVEs

CVE-2025-13213 MEDIUM 5.4 UPGRADE IBM Aspera Orchestrator 3.0.0 through 4.1.2 is vulnerable to HTTP header injection, caused by improper validat
CVE-2023-38001 MEDIUM 6.5 DOWNGRADE IBM Aspera Orchestrator 4.0.1 is vulnerable to cross-site request forgery which could allow an attacker to exe
CVE-2023-26289 MEDIUM 5.4 DOWNGRADE IBM Aspera Orchestrator 4.0.1 is vulnerable to HTTP header injection, caused by improper validation of input b
CVE-2023-26288 MEDIUM 5.5 DOWNGRADE IBM Aspera Orchestrator 4.0.1 does not invalidate session after a password change which could allow an authent

References

← Back to latest CVEs