In Apache HTTP Server 2.4.17 to 2.4.34, by sending continuous, large SETTINGS frames a client can occupy a connection, server thread and CPU time without any connection timeout coming to effect. This affects only HTTP/2 connections. A possible mitigation is to not enable the h2 protocol.
CVE-2018-11763
HIGHNVD 5.97.1▲Elevated
EchelonGraph scoreHIGH confidence
Score elevated to 7.1 because EPSS predicts 51% probability of exploitation within the next 30 days (98th percentile of EPSS-scored CVEs). NVD baseline CVSS 5.9 retained for reference. Confidence: see factors.
Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: epss, ghsa, nvd
7.1EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
- 211 internet-facing services (distinct ip:port) on record running an affected version — derived from Shodan data (© Shodan); a patched service can stay counted while its port stays open
- High exploitation likelihood — EPSS 51%
CISA-KEV: Not listedEPSS PROB: 51%CVSS: 5.9Exploit: Elevated riskExposed services: 211
A fix is available — apply it.
Internet exposure · derived from Shodan data
211 internet-facing services (distinct ip:port) on record running a version that maps to CVE-2018-11763, in our KEV-Exposure radar’s Shodan-derived sample.
across 41 countries (United States, Germany, France, Canada, Netherlands)top: http_server
See the KEV-Exposure radar →Derived from Shodan data. Shodan data is owned by Shodan, which holds its copyright (© Shodan). EchelonGraph claims no ownership of it or copyright in it. Aggregate, host-redacted.
How it counts: every 12 hours, when Shodan query credits allow, the radar runs one Shodan query per tracked product, reads up to 100 ip:port services per query, and keeps a service when its banner version matches a CISA-KEV or high-EPSS CVE; a service is dropped when neither a search nor a Shodan InternetDB port re-check has refreshed it for 21 days. A re-check that finds the port still listed by Shodan InternetDB refreshes the service without re-reading the banner, so a patched service can stay counted while its port stays open. A count is a banner-version inference over a sample, not an exploit test and not an internet-wide census, and the unit is a service, not a machine: a machine answering on two ports counts twice.
- CVSS v3
- 5.9
- EG Score
- 7.1HIGHhigh confidence
- EG Risk
- 57EG Risk 57/100CISA SSVC
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 computedSeverity71% × 45%Exploitation51% × 40%Automatability30% × 15%CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 51%
- EPSS %ILE
- 98th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (EG-KEV: elevated) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
September 25, 2018
Last Modified
November 21, 2024
References (52)
- security@apachehttp://lists.opensuse.org/opensuse-security-announce/2019-06/msg00030.html
- security@apachehttp://lists.opensuse.org/opensuse-security-announce/2019-07/msg00056.html
- security@apachehttp://www.securityfocus.com/bid/105414
- security@apachehttp://www.securitytracker.com/id/1041713
- security@apachehttps://access.redhat.com/errata/RHSA-2018:3558
- security@apachehttps://access.redhat.com/errata/RHSA-2019:0366
- security@apachehttps://access.redhat.com/errata/RHSA-2019:0367
- security@apachehttps://httpd.apache.org/security/vulnerabilities_24.html
- security@apachehttps://lists.apache.org/thread.html/56c2e7cc9deb1c12a843d0dc251ea7fd3e7e80293cde02fcd65286ba%40%3Ccvs.httpd.apache.org%3E
- security@apachehttps://lists.apache.org/thread.html/84a3714f0878781f6ed84473d1a503d2cc382277e100450209231830%40%3Ccvs.httpd.apache.org%3E
- security@apachehttps://lists.apache.org/thread.html/r06f0d87ebb6d59ed8379633f36f72f5b1f79cadfda72ede0830b42cf%40%3Ccvs.httpd.apache.org%3E
- security@apachehttps://lists.apache.org/thread.html/r15f9aa4427581a1aecb4063f1b4b983511ae1c9935e2a0a6876dad3c%40%3Ccvs.httpd.apache.org%3E
- security@apachehttps://lists.apache.org/thread.html/r6521a7f62276340eabdb3339b2aa9a38c5f59d978497a1f794af53be%40%3Ccvs.httpd.apache.org%3E
- security@apachehttps://lists.apache.org/thread.html/r76142b8c5119df2178be7c2dba88fde552eedeec37ea993dfce68d1d%40%3Ccvs.httpd.apache.org%3E
- security@apachehttps://lists.apache.org/thread.html/r9f93cf6dde308d42a9c807784e8102600d0397f5f834890708bf6920%40%3Ccvs.httpd.apache.org%3E
Patch Availability(4)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| ubuntu | apache2-utils (2.4.29-1ubuntu4.4) @ bionic | 2026-05-28 | ubuntu |
| redhat | jbcs-httpd24-openssl-1:1.0.2n-14.jbcs.el7 | 2019-02-18 | redhat |
| redhat | httpd | 2019-02-18 | redhat |
| redhat | httpd24-nghttp2-0:1.7.1-7.el7 | 2018-11-13 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(24 across 24 ecosystems)
Alpine:v3.10(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.15(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.16(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.17(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.18(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.19(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.20(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.21(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.22(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.23(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.24(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.5(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.6(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.7(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.8(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.9(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
All Vendor Advisories
(4)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 5× in last 7d / 22× 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.
Showing the most recent 100 of 141 total refreshes for this CVE.
- 2026-10-09 20:02 UTCEPSS rescore
- 2026-10-07 23:41 UTCEPSS rescore
- 2026-10-06 15:12 UTCEPSS rescore
- 2026-10-05 17:39 UTCEPSS rescore
- 2026-10-03 14:21 UTCEPSS rescore
- 2026-09-30 09:52 UTCEG score recompute
- 2026-09-28 19:42 UTCOSV refresh
- 2026-09-27 13:40 UTCEPSS rescore
- 2026-09-27 13:40 UTCEPSS rescore
- 2026-09-26 15:53 UTCEPSS rescore
- 2026-09-24 13:59 UTCEPSS rescore
- 2026-09-23 13:42 UTCEPSS rescore
- 2026-09-21 20:27 UTCEPSS rescore
- 2026-09-19 15:36 UTCEPSS rescore
- 2026-09-18 19:22 UTCEPSS rescore
- 2026-09-17 19:22 UTCEPSS rescore
- 2026-09-16 14:03 UTCEPSS rescore
- 2026-09-16 05:06 UTCEPSS rescore
- 2026-09-13 16:42 UTCEPSS rescore
- 2026-09-12 14:56 UTCEPSS rescore
- 2026-09-11 14:47 UTCEPSS rescore
- 2026-09-10 09:27 UTCEPSS rescore
- 2026-09-09 00:14 UTCOSV refresh
- 2026-09-06 13:43 UTCEPSS rescore
- 2026-09-05 15:24 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-09-04 13:56 UTCEPSS rescore
- 2026-09-04 05:02 UTCEPSS rescore
- 2026-09-02 14:07 UTCEPSS rescore
- 2026-09-02 14:07 UTCEPSS rescore
- 2026-09-01 13:49 UTCEPSS rescore
- 2026-09-01 03:31 UTCEPSS rescore
- 2026-08-30 19:13 UTCEPSS rescore
- 2026-08-28 21:36 UTCEPSS rescore
- 2026-08-27 14:21 UTCEPSS rescore
- 2026-08-26 14:41 UTCEPSS rescore
- 2026-08-23 00:14 UTCEPSS rescore
- 2026-08-22 09:37 UTCOSV refresh
- 2026-08-21 23:44 UTCEPSS rescore
- 2026-08-20 22:51 UTCEPSS rescore
- 2026-08-19 17:00 UTCEPSS rescore
- 2026-08-18 13:43 UTCEPSS rescore
- 2026-08-17 13:42 UTCEPSS rescore
- 2026-08-16 14:51 UTCEPSS rescore
- 2026-08-16 02:10 UTCEPSS rescore
- 2026-08-15 01:26 UTCEPSS rescore
- 2026-08-13 21:56 UTCEPSS rescore
- 2026-08-12 13:46 UTCEPSS rescore
- 2026-08-11 13:36 UTCEPSS rescore
- 2026-08-08 16:32 UTCEPSS rescore
- 2026-08-07 16:22 UTCEPSS rescore
- 2026-08-06 13:42 UTCEPSS rescore
- 2026-08-06 13:42 UTCEPSS rescore
- 2026-08-06 12:15 UTCOSV refresh
- 2026-08-02 02:23 UTCEPSS rescore
- 2026-07-30 16:24 UTCEPSS rescore
- 2026-07-30 01:27 UTCEPSS rescore
- 2026-07-28 15:32 UTCEPSS rescore
- 2026-07-26 14:51 UTCEPSS rescore
- 2026-07-26 14:51 UTCEPSS rescore
- 2026-07-24 14:14 UTCEPSS rescore
- 2026-07-23 14:15 UTCEPSS rescore
- 2026-07-23 14:15 UTCEPSS rescore
- 2026-07-23 01:32 UTCEG score recompute▲ 1.20
- 2026-07-22 22:12 UTCEG score recompute
- 2026-07-22 14:04 UTCEPSS rescore
- 2026-07-21 15:21 UTCEPSS rescore
- 2026-07-21 05:18 UTCOSV refresh
- 2026-07-20 17:04 UTCEPSS rescore
- 2026-07-20 17:04 UTCEPSS rescore
- 2026-07-19 02:26 UTCEPSS rescore
- 2026-07-19 02:26 UTCEPSS rescore
- 2026-07-16 16:59 UTCEPSS rescore
- 2026-07-16 16:59 UTCEPSS rescore
- 2026-07-15 16:55 UTCEPSS rescore
- 2026-07-15 01:56 UTCEPSS rescore
- 2026-07-13 22:26 UTCEPSS rescore
- 2026-07-13 06:10 UTCEPSS rescore
- 2026-07-12 05:43 UTCEPSS rescore
- 2026-07-11 08:24 UTCEPSS rescore
- 2026-07-09 19:06 UTCEPSS rescore
- 2026-07-08 15:11 UTCEPSS rescore
- 2026-07-06 16:24 UTCEPSS rescore
- 2026-07-06 16:24 UTCEPSS rescore
- 2026-07-04 06:28 UTCEPSS rescore
- 2026-07-04 00:56 UTCOSV refresh
- 2026-07-02 16:54 UTCEPSS rescore
- 2026-07-01 15:03 UTCEPSS rescore
- 2026-07-01 15:03 UTCEPSS rescore
- 2026-06-30 23:19 UTCEPSS rescore
- 2026-06-30 23:19 UTCEPSS rescore
- 2026-06-28 04:53 UTCEPSS rescore
- 2026-06-28 04:53 UTCEPSS rescore
- 2026-06-27 03:06 UTCEPSS rescore
- 2026-06-25 13:47 UTCEPSS rescore
- 2026-06-25 13:47 UTCEPSS rescore
- 2026-06-24 14:02 UTCEPSS rescore
- 2026-06-24 14:02 UTCEPSS rescore
- 2026-06-23 21:30 UTCEPSS rescore
- 2026-06-21 01:57 UTCEPSS rescore
- 2026-06-21 01:57 UTCEPSS rescore
Related CVEs(same product + same vendor)
Same product
10 shownAlpine:v3.5:apache2
- CVE-2018-1312EG 9.8EPSS p97CRITICAL
- CVE-2017-7679EG 9.8EPSS p99CRITICAL
- CVE-2017-3169EG 9.8EPSS p97CRITICAL
- CVE-2017-3167EG 9.8EPSS p97CRITICAL
- CVE-2017-15715NVD 8.1EG 9.0EPSS p100CRITICAL
- CVE-2017-9798NVD 7.5EG 9.0EPSS p100CRITICAL
- CVE-2018-1303NVD 7.5EG 8.6EPSS p99HIGH
- CVE-2018-8011NVD 7.5EG 8.2EPSS p99HIGH
- CVE-2017-7659NVD 7.5EG 8.2EPSS p99HIGH
- CVE-2017-7668NVD 7.5EG 8.2EPSS p99HIGH
Same vendor
10 shownredhat:RHSA-2018:3558 · redhat:RHSA-2019:0366
- CVE-2018-1333EG 7.5EPSS p97HIGH
- CVE-2018-1312EG 9.8EPSS p97CRITICAL
- CVE-2017-15715NVD 8.1EG 9.0EPSS p100CRITICAL
- CVE-2018-1303NVD 7.5EG 8.6EPSS p99HIGH
- CVE-2017-15710EG 7.5EPSS p97HIGH
- CVE-2018-1302EG 5.9EPSS p96MEDIUM
- CVE-2018-1301EG 5.9EPSS p97MEDIUM
- CVE-2018-1283EG 5.3EPSS p95MEDIUM
- CVE-2018-11759NVD 7.5EG 9.0EPSS p100CRITICAL
- CVE-2018-1000168EG 7.5EPSS p96HIGH
Frequently asked(5)
What is CVE-2018-11763?
CVE-2018-11763 is a high vulnerability published on September 25, 2018. In Apache HTTP Server 2.4.17 to 2.4.34, by sending continuous, large SETTINGS frames a client can occupy a connection, server thread and CPU time without any connection timeout coming to effect. This affects only HTTP/2 connections. A possible mitigation is to not enable the h2 protocol.
When was CVE-2018-11763 disclosed?
CVE-2018-11763 was first published on September 25, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-11763 actively exploited?
CVE-2018-11763 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 51% probability of exploitation in the next 30 days (98th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2018-11763?
CVE-2018-11763 has a CVSS v3 base score of 5.9 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.1 (HIGH).
How do I remediate CVE-2018-11763?
A fix for CVE-2018-11763 is available: update to the fixed version the vendor names in its advisory.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2018-11763
Is Your Infrastructure Affected by CVE-2018-11763?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.