{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-13219 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-13219 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-13219 is a medium-severity vulnerability in IBM Aspera Orchestrator, published on 10 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-13219 and fix it if it is affected.\n\nWhat it is: CVE-2025-13219 is a medium-severity vulnerability in IBM Aspera Orchestrator, published on 10 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-13219 in the wild and no public exploit code.\n\nAffected product: IBM Aspera Orchestrator. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-13219/ (Markdown: https://insights.sbomify.com/CVE-2025-13219/index.md)","id":"CVE-2025-13219","markdown":"https://insights.sbomify.com/CVE-2025-13219/index.md","name":"CVE-2025-13219","record":{"aliases":["GHSA-4hf4-8437-8wg9"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Aspera Orchestrator","requires_auth":"none","summary":"Attackers can access sensitive information stored in URL parameters via logs or history, leading to data disclosure in IBM Aspera Orchestrator.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"aspera_orchestrator","vendor":"ibm"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-598","name":"Use of HTTP Request With Sensitive Query String"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Multiple vulnerabilities in IBM Aspera Orchestrator","id":"CVE-2025-13219","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Ultimate Member \u003c= 2.11.0 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode Attributes","id":"CVE-2025-13220"},"packages":[],"prev":{"headline":"Ultimate Member \u003c= 2.11.0 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'value'","id":"CVE-2025-13217"},"products":["Aspera Orchestrator"],"published":"2026-03-10","related":[{"cvss_score":8.8,"headline":"IBM Aspera Orchestrator Command Injection","id":"CVE-2025-13481","kev_date_added":null,"published":"2025-12-11"},{"cvss_score":8.8,"headline":"IBM Aspera Orchestrator command execution","id":"CVE-2023-37407","kev_date_added":null,"published":"2024-05-03"},{"cvss_score":8.1,"headline":"IBM Aspera Orchestrator Unverified Password Change","id":"CVE-2025-13148","kev_date_added":null,"published":"2025-12-11"},{"cvss_score":7.6,"headline":"IBM Aspera Orchestrator SQL Injection","id":"CVE-2025-13214","kev_date_added":null,"published":"2025-12-11"},{"cvss_score":6.5,"headline":"IBM Aspera Orchestrator cross-site request forgery","id":"CVE-2023-38001","kev_date_added":null,"published":"2024-07-30"},{"cvss_score":5.5,"headline":"IBM Aspera Orchestrator session fixation","id":"CVE-2023-26288","kev_date_added":null,"published":"2024-07-30"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-11","vendors":["IBM"]},"summary":"Attackers can access sensitive information stored in URL parameters via logs or history, leading to data disclosure in IBM Aspera Orchestrator.","url":"https://insights.sbomify.com/CVE-2025-13219/"}