CVE-2025-36227
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIBM 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIBM Aspera Faspex 5 versions 5.0.0-5.0.14.3 fails to properly validate or sanitize the Host HTTP header input. Attackers can inject arbitrary headers or poison responses by supplying crafted Host header values, leading to cross-site scripting, cache poisoning, or session hijacking.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 5.0.0, < 5.0.15CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed Faspex versionAccess the IBM Aspera Faspex admin interface and navigate to the About or System Information section to view the software version. Alternatively, check the installation directory for a version file or use the faspex --version command if available via CLI.Affected if The displayed version is 5.0.0 through 5.0.14.3 (any version before 5.0.15).
-
Verify Faspex web service is runningCheck if the IBM Aspera Faspex web application is accessible by attempting to reach the login page or API endpoint over HTTP/HTTPS.Affected if The web interface is accessible and responds to requests, indicating the application is exposed to network traffic.
-
Confirm Host header handling is enabledSend a test HTTP request to the Faspex server with a custom Host header (for example, Host: evil.example.com) and observe whether the application accepts and reflects this header in its response.Affected if The application accepts arbitrary Host header values and reflects them in responses, cache entries, or location headers without validation.
You are affected if the installed IBM Aspera Faspex version is 5.0.0 through 5.0.14.3 and the web interface is accessible over the network.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped5.0.15
Upgrade to IBM Aspera Faspex 5.0.14.4 or later. Until then, consider implementing Web Application Firewall rules to validate Host headers and disable support for user-supplied Host headers where possible.
Aspera Faspex 5.0.15
- 1. Review IBM Aspera Faspex release notes for version 5.0.15 to understand changes and any prerequisites
- 2. Schedule a maintenance window for the upgrade
- 3. Back up the current Faspex configuration and data
- 4. Upgrade Aspera Faspex to version 5.0.15 or later
- 5. Verify the HTTP header injection vulnerability is resolved by testing HOST header handling
- 6. Confirm normal application functionality after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36227 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-36227 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data