HTTP ServerWeb server / proxy · Ibm
CVE-2026-9170
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 HTTP Server 8.5, and 9.0 is vulnerable to denial of service and a potential remote code execution due to improper input validation.
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 · moderate confidenceIBM HTTP Server versions 8.5 and 9.0 contain improper input validation vulnerabilities that can lead to denial of service and potentially enable remote code execution. The critical CVSS score of 9.8 indicates the vulnerability is remotely exploitable with low complexity and no authentication required.
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
HTTP ServerWeb server / proxy
= 8.5.0.0= 9.0.0.0CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify IBM HTTP Server installationRun 'ls -la /opt/IBM/HTTPServer' or check Windows Services for 'IBM HTTP Server' to confirm installation. Use 'adminctl -version' or check version file in the IHS installation directory.Affected if IBM HTTP Server is present on the system
-
Determine installed version numberExecute 'adminctl -version' or check the 'version' file in the IBM HTTP Server installation directory (typically /opt/IBM/HTTPServer/bin or the program directory on Windows).Affected if The version starts with 8.5 or 9.0 (for example, 8.5.0.0 through 8.5.x.x or 9.0.0.0 through 9.0.x.x)
-
Verify HTTP server is network exposedCheck httpd.conf for 'Listen' directives and ensure the server is bound to accessible IP addresses. Review firewall rules and network configuration to confirm the HTTP port is reachable from external sources.Affected if The HTTP server listens on a reachable network interface (0.0.0.0 or external IP) rather than localhost only
-
Review access logs for anomalous input patternsExamine access logs (access_log) for unusual characters, excessive length, or known malicious input patterns in request URIs, headers, or query strings that may indicate exploitation attempts.Affected if Requests contain suspicious input patterns that bypass input validation
If IBM HTTP Server versions 8.5.x or 9.0.x is installed and network-accessible, the environment is likely affected by this vulnerability.
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.
From vendor dataApply IBM HTTP Server security patches as they become available. In the interim, implement strict input validation on all user-supplied data, restrict network exposure, and monitor for anomalous traffic patterns.
Fix this in HTTP Server
Scoped from the published advisory
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9170 — 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-2026-9170 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