CVE-2025-13219

CVE-2025-13219 is a medium-severity vulnerability in Ibm Aspera Orchestrator with a CVSS 3.x base score of 5.9. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-598.

Key facts

Description

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.

Frequently asked questions

What is CVE-2025-13219?
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 severe is CVE-2025-13219?
CVE-2025-13219 has a CVSS 3.x base score of 5.9, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2025-13219 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (25th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-13219?
CVE-2025-13219 affects Ibm Aspera Orchestrator. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-13219?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-13219 have an EU (EUVD) identifier?
Yes. CVE-2025-13219 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-208510.
When was CVE-2025-13219 published?
CVE-2025-13219 was published on 2026-03-10 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Ibm Aspera Orchestrator

All CVEs affecting Ibm Aspera Orchestrator →

Other CWE-598 vulnerabilities

Browse all CWE-598 vulnerabilities →