{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-36227 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-36227 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-36227 is a medium-severity cross-site scripting vulnerability in IBM Aspera Faspex 5, published on 10 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-36227 and fix it if it is affected.\n\nWhat it is: CVE-2025-36227 is a medium-severity cross-site scripting vulnerability in IBM Aspera Faspex 5, published on 10 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-36227 in the wild and no public exploit code.\n\nAffected product: IBM Aspera Faspex 5. 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-36227/ (Markdown: https://insights.sbomify.com/CVE-2025-36227/index.md)","id":"CVE-2025-36227","markdown":"https://insights.sbomify.com/CVE-2025-36227/index.md","name":"CVE-2025-36227","record":{"aliases":["GHSA-4cv3-8w5r-6g5r"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Aspera Faspex","requires_auth":"low_privilege","summary":"Attackers can inject HTTP headers to perform cross-site scripting, cache poisoning, or session hijacking against IBM Aspera Faspex users.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"aspera_faspex","vendor":"ibm"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-644","name":"Improper Neutralization of HTTP Headers for Scripting Syntax"}],"description":"IBM Aspera Faspex 5 5.0.0 through 5.0.14.3 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.","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 Faspex","id":"CVE-2025-36227","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Incorrect Execution-Assigned Permissions in IBM Aspera Faspex","id":"CVE-2025-36228"},"packages":[],"prev":{"headline":"Multiple vulnerabilities in IBM Aspera Faspex","id":"CVE-2025-36226"},"products":["Aspera Faspex 5"],"published":"2026-03-10","related":[{"cvss_score":9.8,"headline":"IBM Aspera Faspex Code Execution","id":"CVE-2022-47986","kev_date_added":"2023-02-21","published":"2023-02-17"},{"cvss_score":9.9,"headline":"IBM Aspera Faspex XML external entity injection","id":"CVE-2023-27874","kev_date_added":null,"published":"2023-03-21"},{"cvss_score":9.1,"headline":"OS command injection in IBM Aspera Faspex","id":"CVE-2026-14958","kev_date_added":null,"published":"2026-07-28"},{"cvss_score":9.1,"headline":"OS Command Injection in IBM Aspera Faspex","id":"CVE-2026-14959","kev_date_added":null,"published":"2026-07-28"},{"cvss_score":8.2,"headline":"Multiple vulnerabilities in IBM Aspera Faspex","id":"CVE-2026-14996","kev_date_added":null,"published":"2026-07-28"},{"cvss_score":7.8,"headline":"IBM Aspera Faspex privilege escalation","id":"CVE-2023-37400","kev_date_added":null,"published":"2024-04-19"},{"cvss_score":7.5,"headline":"IBM Aspera Faspex improper access control","id":"CVE-2023-30995","kev_date_added":null,"published":"2023-09-08"}],"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-10","vendors":["IBM"]},"summary":"Attackers can inject HTTP headers to perform cross-site scripting, cache poisoning, or session hijacking against IBM Aspera Faspex users.","url":"https://insights.sbomify.com/CVE-2025-36227/"}