CVE-2018-17189
No exploitation reported by the sources we read.
- Published2019-01-30
- WeaknessCWE-400
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
In Apache HTTP server versions 2.4.37 and prior, by sending request bodies in a slow loris way to plain resources, the h2 stream for that request unnecessarily occupied a server thread cleaning up that incoming data. This affects only HTTP/2 (mod_http2) connections.
Timeline
dates in UTC- 2019-01-3022:29CVE publishedNVD
- 2026-10-2319:23EPSS crossed 10 %FIRST EPSS
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2018-17189?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2018-17189?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2.4 | = 2.4.17 | no fix published | NVD |
| 2.4 | = 2.4.18 | no fix published | NVD |
| 2.4 | = 2.4.20 | no fix published | NVD |
| 2.4 | = 2.4.23 | no fix published | NVD |
| 2.4 | = 2.4.25 | no fix published | NVD |
| 2.4 | = 2.4.26 | no fix published | NVD |
| 2.4 | = 2.4.27 | no fix published | NVD |
| 2.4 | = 2.4.28 | no fix published | NVD |
| 2.4 | = 2.4.29 | no fix published | NVD |
| 2.4 | = 2.4.30 | no fix published | NVD |
| 2.4 | = 2.4.33 | no fix published | NVD |
| 2.4 | = 2.4.34 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 14.4 | = 14.04 | no fix published | NVD |
| 16.4 | = 16.04 | no fix published | NVD |
| 18.4 | = 18.04 | no fix published | NVD |
| 18.10 | = 18.10 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 17.1 | = 17.1 | no fix published | NVD |
| 17.2 | = 17.2 | no fix published | NVD |
| 17.3 | = 17.3 | no fix published | NVD |
9 more products in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
Advisories and patches
- httpd.apache.orgVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.15.3read 2026-10-23
- NVDCVSS 2.05read 2026-10-23
- NVDweakness (CWE)CWE-400read 2026-10-23
- FIRST EPSSEPSS score20.1 %read 2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- Published
- 2019-01-30
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2018-17189?
Is CVE-2018-17189 actively exploited?
What is the CVSS score for CVE-2018-17189?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.