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.
CVE-2025-36227
MEDIUMPre-NVD 5.45.4—Trending — 3 sources updated this week
EchelonGraph scoreMEDIUM confidence
Score 5.4 from GitHub Security Advisory published 2026-03-10. a secondary CVSS source baseline 5.4; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.4Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.4
- EG Score
- 5.4(medium)
- EG Risk
- 29(Track)EG Risk 29/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity54% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 11%
- KEV
- Not listed
Published
March 10, 2026
Last Modified
June 17, 2026
References (1)
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-30 16:27 UTCEPSS rescore
- 2026-07-30 01:29 UTCEPSS rescore
- 2026-07-28 15:35 UTCEPSS rescore
- 2026-07-27 13:44 UTCEG score recompute
- 2026-07-27 13:44 UTCGHSA enrichment
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2025-36227?
CVE-2025-36227 is a medium vulnerability published on March 10, 2026. 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.
When was CVE-2025-36227 disclosed?
CVE-2025-36227 was first published in the National Vulnerability Database on March 10, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-36227 actively exploited?
CVE-2025-36227 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 88.7% of all scored CVEs.
What is the CVSS score of CVE-2025-36227?
CVE-2025-36227 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2025-36227?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-36227, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2025-36227
Is Your Infrastructure Affected by CVE-2025-36227?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.