CVE-2017-7529

HIGHNVD 7.59.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 92% probability of exploitation within the next 30 days (top 0.3% of all CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Elevated
7.5
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 15 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 63%
CISA-KEV: Not listedEPSS: 63%CVSS: 7.5Exploit: NoneExposed: 15

A fix is available — apply it.

Nginx versions since 0.5.6 up to and including 1.13.2 are vulnerable to integer overflow vulnerability in nginx range filter module resulting into leak of potentially sensitive information triggered by specially crafted request.

Live · internet exposure

15 internet-exposed hosts are running an affected version of CVE-2017-7529 right now.

across 10 countries (United States, China, Indonesia, Ghana, Hong Kong)top: nginx
See the live KEV-Exposure radar →Found passively from public internet-scan data — aggregate, host-redacted.

EchelonGraph is the only CVE feed that fuses live vulnerability intelligence with its own live internet-exposure radar — so you see not just that a CVE is exploited, but how much of the internet is exposed to it right now.

CVSS v3
7.5
EG Score
9.0(high)
EPSS
99.1%
KEV
Not listed

Published

July 13, 2017

Last Modified

May 13, 2026

References (14)

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntunginx-light (1.10.3-0ubuntu0.16.04.2) @ xenial2026-05-22ubuntu
redhatrh-nginx110-nginx-1:1.10.2-8.el72017-08-28redhat

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.

All Vendor Advisories

(2)

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 / 27× 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.

  1. 2026-07-06 16:24 UTCEPSS rescore
  2. 2026-07-06 16:24 UTCEPSS rescore
  3. 2026-07-05 02:27 UTCEPSS rescore
  4. 2026-07-02 16:54 UTCEPSS rescore
  5. 2026-07-01 15:03 UTCEPSS rescore
  6. 2026-06-28 04:53 UTCEPSS rescore
  7. 2026-06-28 04:53 UTCEPSS rescore
  8. 2026-06-27 03:06 UTCEPSS rescore
  9. 2026-06-25 13:47 UTCEPSS rescore
  10. 2026-06-24 14:02 UTCEPSS rescore
  11. 2026-06-24 14:02 UTCEPSS rescore
  12. 2026-06-23 21:30 UTCEPSS rescore
  13. 2026-06-23 21:30 UTCEPSS rescore
  14. 2026-06-23 03:30 UTCOSV refresh
  15. 2026-06-22 14:23 UTCEPSS rescore
  16. 2026-06-22 14:23 UTCEPSS rescore
  17. 2026-06-21 01:57 UTCEPSS rescore
  18. 2026-06-21 01:57 UTCEPSS rescore
  19. 2026-06-18 17:50 UTCEPSS rescore
  20. 2026-06-17 17:50 UTCEPSS rescore
  21. 2026-06-16 17:50 UTCEPSS rescore
  22. 2026-06-15 17:45 UTCEPSS rescore
  23. 2026-06-14 23:14 UTCEPSS rescore
  24. 2026-06-14 23:14 UTCEPSS rescore
  25. 2026-06-12 23:09 UTCEPSS rescore
Show 30 more
  1. 2026-06-12 23:09 UTCEPSS rescore
  2. 2026-06-10 22:15 UTCEPSS rescore
  3. 2026-06-06 13:45 UTCEPSS rescore
  4. 2026-06-06 13:45 UTCEPSS rescore
  5. 2026-06-06 00:23 UTCOSV refresh
  6. 2026-06-05 22:44 UTCEPSS rescore
  7. 2026-06-05 22:44 UTCEPSS rescore
  8. 2026-06-05 06:08 UTCEPSS rescore
  9. 2026-06-05 06:08 UTCEPSS rescore
  10. 2026-06-02 20:11 UTCEPSS rescore
  11. 2026-06-02 20:11 UTCEPSS rescore
  12. 2026-05-29 13:41 UTCEPSS rescore
  13. 2026-05-28 13:42 UTCEPSS rescore
  14. 2026-05-28 13:42 UTCEPSS rescore
  15. 2026-05-22 21:15 UTCEPSS rescore
  16. 2026-05-22 21:15 UTCEPSS rescore
  17. 2026-05-22 21:15 UTCEPSS rescore
  18. 2026-05-22 21:15 UTCEPSS rescore
  19. 2026-05-22 21:15 UTCEPSS rescore
  20. 2026-05-22 21:15 UTCEPSS rescore
  21. 2026-05-22 21:15 UTCEPSS rescore
  22. 2026-05-22 11:49 UTCEG score recompute
  23. 2026-05-22 11:49 UTCVendor advisory
  24. 2026-05-22 11:49 UTCGHSA enrichment
  25. 2026-05-22 10:04 UTCOSV refresh
  26. 2026-05-21 22:40 UTCEPSS rescore
  27. 2026-05-21 22:40 UTCEPSS rescore
  28. 2026-05-18 21:30 UTCEPSS rescore
  29. 2026-05-18 21:30 UTCEPSS rescore
  30. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(6 references)

Working exploit code is in the public domain (6 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCShehzadcyber/CVE-2017-7529
    First seen Jul 18, 2022

    Nginx versions since 0.5.6 up to and including 1.13.2 are vulnerable to integer overflow vulnerability in nginx range filter module resulting into leak of potentially sensitive information triggered by specially crafted request.

    Open source ↗
  • GitHub PoCgemboxteam/exploit-nginx-1.10.3
    First seen Jan 19, 2021

    CVE-2017-7529 | nginx on the range 0.5.6 - 1.13.2

    Open source ↗
  • GitHub PoCcyberharsh/nginx-CVE-2017-7529
    First seen Jun 24, 2020
    Open source ↗
  • GitHub PoCMaxSecurity/CVE-2017-7529-POC
    First seen Jun 6, 2019
    Open source ↗
  • GitHub PoCen0f/CVE-2017-7529_PoC
    First seen Jun 20, 2018

    CVE-2017-7529_PoC

    Open source ↗
  • GitHub PoCliusec/CVE-2017-7529
    First seen Jul 19, 2017
    Open source ↗

Frequently asked(5)

What is CVE-2017-7529?
CVE-2017-7529 is a high vulnerability published on July 13, 2017. Nginx versions since 0.5.6 up to and including 1.13.2 are vulnerable to integer overflow vulnerability in nginx range filter module resulting into leak of potentially sensitive information triggered by specially crafted request.
When was CVE-2017-7529 disclosed?
CVE-2017-7529 was first published in the National Vulnerability Database on July 13, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-7529 actively exploited?
CVE-2017-7529 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-7529?
CVE-2017-7529 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.
How do I remediate CVE-2017-7529?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-7529, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-7529

Explore →

Is Your Infrastructure Affected by CVE-2017-7529?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs