Apache httpd allows remote attackers to read secret data from process memory if the Limit directive can be set in a user's .htaccess file, or if httpd.conf has certain misconfigurations, aka Optionsbleed. This affects the Apache HTTP Server through 2.2.34 and 2.4.x through 2.4.27. The attacker sends an unauthenticated OPTIONS HTTP request when attempting to read secret data. This is a use-after-free issue and thus secret data is not always sent, and the specific data depends on many factors including configuration. Exploitation with .htaccess can be blocked with a patch to the ap_limit_section function in server/core.c.
CVE-2017-9798
CRITICALNVD 7.59.0Trending — 4 sources updated this weekWeaponizedEG-KEV Tier 2: WeaponizedEG-KEV is EchelonGraph's own tiering of exploitation signals from CISA KEV, CISA's SSVC data (Vulnrichment), ransomware data, public exploit-code references and EPSS.Tier 2 is not evidence of exploitation. It means a Metasploit module exists, or Exploit-DB marks a public exploit verified, or CISA's SSVC data says "public PoC" and EPSS is 50% or more. EchelonGraph does not test whether exploit code works.Signals for this CVE: a Metasploit module, EPSS in the top 5%, EPSS 50% or more, other public exploit code (a GitHub or vendor proof of concept, or an Exploit-DB entry not marked verified).First public exploit code on record: 2017-09-18 (Exploit-DB EDB-42745)EchelonGraph confidence 70%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreHIGH confidence
“▲” beside the score: it is higher than NVD's CVSS score.
Score elevated to 9.0 because EPSS predicted 95% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.
Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
9.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
- 508 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 95%
- Public exploit code is available (Metasploit, other public proof-of-concept code)
CISA-KEV: Not listedEPSS PROB: 95%CVSS: 7.5Exploit: Metasploit · other public PoCExposed services: 508
A fix is available — apply it.
Internet exposure · derived from Shodan data
508 internet-facing services (distinct ip:port) on record running a version that maps to CVE-2017-9798, in our KEV-Exposure radar’s Shodan-derived sample.
across 60 countries (United States, Poland, Germany, Japan, 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
- 7.5
- EG Score
- 9.0CRITICALhigh confidence
- EG Risk
- 72EG Risk 72/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity75% × 45%Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation95% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.Exploitation public PoC (exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.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
- 95%
- EPSS %ILE
- 99th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 7.5 HIGH): a likelihood of exploitation, not impact.
- EG Severity
- 7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 95% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-22). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.
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 (exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
September 18, 2017
Last Modified
June 17, 2026
Advisory Details (4)
Auto-updated Oct 14, 2026🔬 Proof of concept available. Patch available. Sources: redhat.
Red HatMentions a patch (unverified)
Affected: Red Hat Enterprise Linux 7.
https://access.redhat.com/errata/RHSA-2017:2882Web page🟡 PoC Available
oss-security - Optionsbleed bug in Apache HTTPD
http://openwall.com/lists/oss-security/2017/09/18/2Vendor Advisories for CVE-2017-9798(5)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2017:3240Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 6.4.18 security update
- RHSA-2017:3239Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 6.4.18 security update
- RHSA-2017:3113Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat JBoss Web Server security and bug fix update
- RHSA-2017:3114Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat JBoss Web Server security and bug fix update
- RHSA-2017:2972Red Hat Product SecurityMedium
Red Hat Security Advisory: httpd security update
Patch Availability(14)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| ubuntu | apache2.2-bin (2.2.22-1ubuntu1.14) @ precise | 2026-10-22 | ubuntu |
| ubuntu | libapache2-mod-proxy-html (1:2.4.7-1ubuntu4.18) @ trusty | 2026-10-22 | ubuntu |
| redhat | httpd | 2017-12-15 | redhat |
| redhat | jbcs-httpd24-mod_cluster-native-0:1.3.8-1.Final_redhat_1.jbcs.el7 | 2017-12-15 | redhat |
| redhat | jbcs-httpd24-mod_cluster-native-0:1.3.8-1.Final_redhat_1.jbcs.el6 | 2017-12-15 | redhat |
| redhat | mod_cluster-native-0:1.2.13-9.Final_redhat_2.ep6.el7 | 2017-11-16 | redhat |
| redhat | httpd-0:2.4.6-45.el7_3.5 | 2017-11-13 | redhat |
| redhat | httpd-0:2.4.6-40.el7_2.6 | 2017-11-13 | redhat |
| redhat | httpd-0:2.2.15-47.el6_7.5 | 2017-11-13 | redhat |
| redhat | tomcat7-0:7.0.54-28_patch_05.ep6.el7 | 2017-11-02 | redhat |
| redhat | patch | 2017-11-02 | redhat |
| redhat | httpd24-nghttp2-0:1.7.1-6.el7 | 2017-10-24 | redhat |
| redhat | httpd-0:2.2.15-60.el6_9.6 | 2017-10-19 | redhat |
| redhat | httpd-0:2.4.6-67.el7_4.5 | 2017-10-11 | 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
(29 across 29 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.3(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | — |
| — |
Alpine:v3.4(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 | — |
| — |
Debian:7(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | 2.2.22-13 ... 2.2.22-13+deb7u9 (12 versions) |
| — |
Debian:8(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | 2.4.10-10 ... 2.4.10-10+deb8u9 (11 versions) |
| — |
Debian:9(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache2 | 2.4.25-3, 2.4.25-3+deb9u1, 2.4.25-3+deb9u2 |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(10)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
- Red HatRHSA-2017:2882MODERATE2017-09-18
RHSA-2017:2882 — Moderate
- Red HatRHSA-2017:3018MODERATE2017-09-18
RHSA-2017:3018 — Moderate
- Red HatRHSA-2017:3193MODERATE2017-09-18
RHSA-2017:3193 — Moderate
- Red HatRHSA-2017:3194MODERATE2017-09-18
RHSA-2017:3194 — Moderate
- Red HatRHSA-2017:3195MODERATE2017-09-18
RHSA-2017:3195 — Moderate
- Red HatRHSA-2017:3475MODERATE2017-09-18
RHSA-2017:3475 — Moderate
- Red HatRHSA-2017:3476MODERATE2017-09-18
RHSA-2017:3476 — Moderate
- Red HatRHSA-2017:3477MODERATE2017-09-18
RHSA-2017:3477 — Moderate
- UbuntuUSN-3425-1MEDIUM
Apache HTTP Server vulnerability
- UbuntuUSN-3425-2MEDIUM
Apache HTTP Server vulnerability
Data Freshness Timeline
(refreshed 22× in last 7d / 41× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 15 repeat rows among the latest 95 are merged into the row they repeat.
- 2026-10-22 20:25 UTCEG score recompute
- 2026-10-22 20:25 UTCVendor advisory
- 2026-10-22 20:25 UTCGHSA enrichmentGHSA-jxf6-fx3m-8x2r · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-21 19:30 UTCEG score recompute
- 2026-10-21 19:30 UTCVendor advisory
- 2026-10-21 19:30 UTCGHSA enrichmentGHSA-jxf6-fx3m-8x2r · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-21 16:27 UTCEPSS rescoreEPSS 95% · 99th percentile
- 2026-10-20 18:36 UTCEG score recompute
- 2026-10-20 18:36 UTCVendor advisory
- 2026-10-20 18:35 UTCGHSA enrichmentGHSA-jxf6-fx3m-8x2r · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-19 17:40 UTCEG score recompute
- 2026-10-19 17:40 UTCVendor advisory
- 2026-10-19 17:40 UTCGHSA enrichmentGHSA-jxf6-fx3m-8x2r · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-18 16:44 UTCEG score recompute
- 2026-10-18 16:44 UTCVendor advisory
- 2026-10-18 16:43 UTCGHSA enrichmentGHSA-jxf6-fx3m-8x2r · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-18 07:42 UTCEG score recompute
- 2026-10-18 07:42 UTCVendor advisory
- 2026-10-18 07:42 UTCGHSA enrichmentGHSA-jxf6-fx3m-8x2r · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-17 06:45 UTCEG score recompute
- 2026-10-17 06:45 UTCVendor advisory
- 2026-10-17 06:45 UTCGHSA enrichmentGHSA-jxf6-fx3m-8x2r · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-16 05:49 UTCEG score recompute
- 2026-10-16 05:49 UTCVendor advisory
- 2026-10-16 05:48 UTCGHSA enrichmentGHSA-jxf6-fx3m-8x2r · GitHub severity HIGH · GitHub CVSS 7.5
Show 55 moreShow fewer
- 2026-10-15 04:19 UTCEG score recompute
- 2026-10-15 04:19 UTCVendor advisory
- 2026-10-15 04:19 UTCGHSA enrichmentGHSA-jxf6-fx3m-8x2r · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-14 16:27 UTCEPSS rescoreEPSS 95% · 99th percentile
- 2026-10-14 00:18 UTCEG score recompute
- 2026-10-14 00:18 UTCVendor advisory
- 2026-10-14 00:18 UTCGHSA enrichmentGHSA-jxf6-fx3m-8x2r · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-12 20:24 UTCVendor advisory
- 2026-10-12 20:24 UTCGHSA enrichmentGHSA-jxf6-fx3m-8x2r · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-12 20:23 UTCEG score recompute
- 2026-10-12 00:47 UTCEG score recompute
- 2026-10-08 00:24 UTCOSV refresh
- 2026-10-05 17:39 UTCEPSS rescoreEPSS 95% · 99th percentile
- 2026-09-30 09:49 UTCEG score recompute
- 2026-09-28 13:45 UTCEPSS rescoreEPSS 95% · 99th percentile
- 2026-09-24 13:59 UTCEPSS rescoreEPSS 95% · 99th percentile
- 2026-09-21 20:27 UTCEPSS rescoreEPSS 95% · 99th percentile
- 2026-09-18 06:20 UTCOSV refresh
- 2026-09-07 15:56 UTCEPSS rescoreEPSS 95% · 99th percentile
- 2026-09-04 05:02 UTCEPSS rescoreEPSS 95% · 99th percentile
- 2026-08-30 19:13 UTCEPSS rescoreEPSS 95% · 99th percentile
- 2026-08-30 06:30 UTCOSV refresh
- 2026-08-28 21:36 UTCEPSS rescoreEPSS 95% · 99th percentile
- 2026-08-16 02:10 UTCEPSS rescoreEPSS 95% · 99th percentile
- 2026-08-13 22:04 UTCOSV refresh
- 2026-08-02 02:23 UTCEPSS rescoreEPSS 95% · 99th percentile
- 2026-07-29 01:17 UTCOSV refresh
- 2026-07-26 14:51 UTCEPSS rescoreEPSS 95% · 99th percentile
- 2026-07-23 01:31 UTCEG score recompute
- 2026-07-22 22:11 UTCEG score recompute
- 2026-07-22 14:04 UTCEPSS rescoreEPSS 95% · 99th percentile
- 2026-07-20 17:04 UTCEPSS rescoreEPSS 95% · 99th percentile
- 2026-07-19 02:26 UTCEPSS rescoreEPSS 95% · 99th percentile
- 2026-07-11 17:41 UTCOSV refresh
- 2026-07-01 15:03 UTCEPSS rescoreEPSS 95% · 99th percentile
- 2026-06-30 23:19 UTCEPSS rescoreEPSS 95% · 99th percentile
- 2026-06-28 04:53 UTCEPSS rescoreEPSS 95% · 99th percentile
- 2026-06-23 00:00 UTCOSV refresh
- 2026-06-22 14:23 UTCEPSS rescoreEPSS 95% · 99th percentile
- 2026-06-21 01:57 UTCEPSS rescoreEPSS 95% · 99th percentile
- 2026-06-18 17:50 UTCEPSS rescoreEPSS 95% · 99th percentile
- 2026-06-17 17:50 UTCEPSS rescoreEPSS 95% · 99th percentile
- 2026-06-15 17:45 UTCEPSS rescoreEPSS 95% · 99th percentile
- 2026-06-14 23:14 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-06-05 18:27 UTCOSV refresh
- 2026-06-04 13:10 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-05-31 22:28 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-05-29 13:41 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-05-27 13:38 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-05-26 07:17 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-05-22 09:45 UTCEG score recompute
- 2026-05-22 09:45 UTCVendor advisory
- 2026-05-22 09:45 UTCGHSA enrichmentGHSA-jxf6-fx3m-8x2r · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-05-21 22:40 UTCEPSS rescoreEPSS 94% · 99th percentile
- 2026-05-18 21:30 UTCEPSS rescoreEPSS 94% · 99th percentile
Publicly available exploits
(5 references)Public exploit code is referenced for this CVE (1 Metasploit module, 1 Exploit-DB entry, 2 GitHub PoCs), as is 1 GitHub checker repository. A GitHub repository named or described as a checker or scanner checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.
- Metasploitauxiliary/scanner/http/apache_optionsbleed✓ verifiedPublished Dec 8, 2017
Apache Optionsbleed Scanner
Open source ↗ - GitHub PoCbrokensound77/OptionsBleed-POC-ScannerPublished Sep 27, 2017
OptionsBleed (CVE-2017-9798) PoC / Scanner
Open source ↗ - GitHub PoCpabloec20/optionsbleedPublished Sep 20, 2017
CVE-2017-9798
Open source ↗ - Exploit-DBEDB-42745Published Sep 18, 2017
Apache < 2.2.34 / < 2.4.27 - OPTIONS Memory Leak
Open source ↗ - GitHub checkernitrado/CVE-2017-9798Published Sep 18, 2017
Checks a shared hosting environment for CVE-2017-9798
Open source ↗
Related CVEs(same product + same vendor + same CWE)· as of October 22, 2026
Same product
10 shownAlpine:v3.3:apache2 · Alpine:v3.4:apache2
- CVE-2017-7679EG 9.8EPSS p99CRITICAL
- CVE-2017-3169EG 9.8EPSS p97CRITICAL
- CVE-2017-3167EG 9.8EPSS p97CRITICAL
- CVE-2017-7668NVD 7.5EG 8.2EPSS p99HIGH
- CVE-2018-1312EG 9.8EPSS p97CRITICAL
- CVE-2017-15710EG 7.5EPSS p97HIGH
- CVE-2018-1301EG 5.9EPSS p97MEDIUM
- CVE-2017-15715NVD 8.1EG 9.0EPSS p100CRITICAL
- CVE-2018-1303NVD 7.5EG 8.6EPSS p99HIGH
- CVE-2018-1283EG 5.3EPSS p96MEDIUM
Same vendor
10 shownredhat:RHSA-2017:3113 · redhat:RHSA-2017:3193 · redhat:RHSA-2017:3475
- CVE-2017-9788EG 9.1EPSS p99CRITICAL
- CVE-2017-7679EG 9.8EPSS p99CRITICAL
- CVE-2017-3169EG 9.8EPSS p97CRITICAL
- CVE-2017-3167EG 9.8EPSS p97CRITICAL
- CVE-2016-2183NVD 7.5EG 9.0EPSS p100CRITICAL
- CVE-2017-12613EG 7.1HIGH
- CVE-2017-12617NVD 8.1EG 9.0 KEVEPSS p100CRITICAL
- CVE-2017-12615NVD 8.1EG 9.0 KEVEPSS p100CRITICAL
- CVE-2017-7668NVD 7.5EG 8.2EPSS p99HIGH
- CVE-2017-12171EG 6.5EPSS p95MEDIUM
Frequently asked(5)
What is CVE-2017-9798?
CVE-2017-9798 is a critical-severity vulnerability; its CVE record was published on September 18, 2017. Apache httpd allows remote attackers to read secret data from process memory if the Limit directive can be set in a user's .htaccess file, or if httpd.conf has certain misconfigurations, aka Optionsbleed. This affects the Apache HTTP Server through 2.2.34 and 2.4.x through 2.4.27. The attacker…
When was CVE-2017-9798 made public?
CVE-2017-9798 was made public on September 18, 2017: that is the date its CVE record's CNA, Apache Software Foundation, gives for when the vulnerability was made public. The CVE record itself was published on September 18, 2017. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2017-9798 actively exploited?
CVE-2017-9798 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: a Metasploit module exists for it. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 95% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-9798?
CVE-2017-9798 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
How do I remediate CVE-2017-9798?
A fix for CVE-2017-9798 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2017-9798 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-9798
Is Your Infrastructure Affected by CVE-2017-9798?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.