VulnerabilityPublished 10 Mar 2026

CVE-2025-13219: IBM Aspera Orchestrator · Use of GET Request Method With Sensitive Query Strings

Affects IBM Aspera OrchestratorSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.9 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

5.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
IBMAspera Orchestrator	Affected >=3.0.0 <=4.1.2	Fixed in–
Mavencom.ibm/aspera-orchestrator`pkg:maven/com.ibm/aspera-orchestrator`Other threats	Affected =3.0.0	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:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability, organizations should immediately review and modify their use of IBM Aspera Orchestrator to avoid transmitting sensitive information in URL query strings. This can include switching to POST requests for sensitive data, using secure cookies or headers for authentication tokens, and implementing URL rewriting or parameter encryption if feasible. Administrators should audit web server and proxy logs to identify exposure of sensitive data and restrict access to these logs to authorized personnel only. Browser history and referrer leakage can be minimized by implementing Content Security Policy (CSP) directives and referrer policy headers to limit referrer data sent to third parties. IBM should be contacted for official patches or updates, and organizations should monitor IBM security advisories for fixes. Additionally, network segmentation and strict access controls around systems handling Aspera Orchestrator logs can reduce the risk of unauthorized access. Regular security training to raise awareness about secure URL handling practices is also recommended.

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.

Impact

The primary impact of this vulnerability is the potential disclosure of sensitive information such as credentials, tokens, or proprietary data embedded in URL query parameters. If attackers or unauthorized users gain access to server logs, browser histories, or referrer headers, they can harvest this information to facilitate further attacks such as unauthorized access, session hijacking, or data exfiltration. Organizations relying on IBM Aspera Orchestrator for secure file transfer and orchestration may face increased risk of data leakage, undermining confidentiality and trust. Although integrity and availability are not directly affected, the exposure of sensitive data can lead to broader security incidents. The medium severity rating reflects the need for attackers to have access to logs or browsing data, which may limit exploitation but does not eliminate risk, especially in environments with shared or poorly secured infrastructure. The lack of known exploits suggests limited current active threat but does not preclude future exploitation as awareness grows.

CWE-598Use of HTTP Request With Sensitive Query String (opens in a new tab)
Variant weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The web application uses an HTTP method to process a request, but the request includes sensitive information in the query string.
Implementation
When sending sensitive information, only include it in the request body or request headers instead of the query string. This may require avoiding use of GET requests.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Web Service Security (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V3.1.1 (opens in a new tab)
V13.1.3 (opens in a new tab)
V8.3.4 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

ibm.com/support/pages/node/7263083 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

CPE configurations (2)

Description

AI analysisMachine-generated, updated 11 Mar 2026, 14:45 UTC

WeaknessesCWE-598

Technical details

References

Community reviews

Related threats