CVE-2016-0742

HIGHNVD 7.58.9▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.9 because EPSS predicts 82% probability of exploitation within the next 30 days (top 0.4% 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
8.9EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 25 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 82%
CISA-KEV: Not listedEPSS PROB: 82%CVSS: 7.5Exploit: Elevated riskExposed: 25

A fix is available — apply it.

The resolver in nginx before 1.8.1 and 1.9.x before 1.9.10 allows remote attackers to cause a denial of service (invalid pointer dereference and worker process crash) via a crafted UDP DNS response.

Live · internet exposure

25 internet-exposed hosts are running an affected version of CVE-2016-0742 right now.

across 13 countries (United States, China, Italy, Indonesia, Canada)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
8.9(high)
EG Risk
77(Track)
EG Risk 77/100SSVC: Track

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 computed
Severity89% × 45%
Exploitation82% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
82%
EPSS %ILE
100%
KEV
Not listed

Published

February 15, 2016

Last Modified

June 17, 2026

References (22)

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntunginx-light (1.9.3-1ubuntu1.1) @ wily2026-05-22ubuntu
redhatrh-nginx18-nginx-1:1.8.1-1.el72016-07-14redhat

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

(7 across 7 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
nginx—1.9.10-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
nginx—1.9.10-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
nginx—1.9.10-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
nginx—1.9.10-1—
Debian:6.0(1)
PackageVulnerable rangeFixed inDependents
nginx0.7.67-3, 0.7.67-3+squeeze1, 0.7.67-3+squeeze2, 0.7.67-3+squeeze3, 0.7.67-3+squeeze40.7.67-3+squeeze4+deb6u1—
Debian:7(1)
PackageVulnerable rangeFixed inDependents
nginx1.2.1-2.2, 1.2.1-2.2+wheezy1, 1.2.1-2.2+wheezy2, 1.2.1-2.2+wheezy3, 1.2.1-2.2+wheezy3~bpo60+11.2.1-2.2+wheezy4—
Debian:8(1)
PackageVulnerable rangeFixed inDependents
nginx1.6.2-5, 1.6.2-5+a.exp1, 1.6.2-5+deb8u1~bpo70+11.6.2-5+deb8u1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

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 4× in last 7d / 13× 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-09-19 02:36 UTCOSV refresh
  2. 2026-09-18 19:22 UTCEPSS rescore
  3. 2026-09-17 19:21 UTCEPSS rescore
  4. 2026-09-15 03:05 UTCEPSS rescore
  5. 2026-09-10 09:26 UTCEPSS rescore
  6. 2026-09-07 15:56 UTCEPSS rescore
  7. 2026-09-06 13:42 UTCEPSS rescore
  8. 2026-09-04 13:55 UTCEPSS rescore
  9. 2026-09-02 14:07 UTCEPSS rescore
  10. 2026-08-31 06:19 UTCOSV refresh
  11. 2026-08-27 14:20 UTCEPSS rescore
  12. 2026-08-26 14:41 UTCEPSS rescore
  13. 2026-08-21 23:44 UTCEPSS rescore
  14. 2026-08-19 16:59 UTCEPSS rescore
  15. 2026-08-16 02:09 UTCEPSS rescore
  16. 2026-08-15 01:25 UTCEPSS rescore
  17. 2026-08-14 13:24 UTCOSV refresh
  18. 2026-08-12 13:46 UTCEPSS rescore
  19. 2026-08-04 15:04 UTCEPSS rescore
  20. 2026-07-30 02:24 UTCOSV refresh
  21. 2026-07-26 14:50 UTCEPSS rescore
  22. 2026-07-25 14:13 UTCEPSS rescore
  23. 2026-07-24 14:13 UTCEPSS rescore
  24. 2026-07-23 01:20 UTCEG score recompute
  25. 2026-07-23 00:22 UTCEG score recompute▲ 1.40
Show 59 more
  1. 2026-07-22 22:00 UTCEG score recompute
  2. 2026-07-22 14:04 UTCEPSS rescore
  3. 2026-07-20 17:03 UTCEPSS rescore
  4. 2026-07-16 16:59 UTCEPSS rescore
  5. 2026-07-15 16:54 UTCEPSS rescore
  6. 2026-07-15 16:54 UTCEPSS rescore
  7. 2026-07-12 11:37 UTCOSV refresh
  8. 2026-07-09 19:05 UTCEPSS rescore
  9. 2026-07-09 19:05 UTCEPSS rescore
  10. 2026-07-04 06:28 UTCEPSS rescore
  11. 2026-07-01 15:02 UTCEPSS rescore
  12. 2026-06-25 13:47 UTCEPSS rescore
  13. 2026-06-25 13:47 UTCEPSS rescore
  14. 2026-06-24 14:02 UTCEPSS rescore
  15. 2026-06-24 14:02 UTCEPSS rescore
  16. 2026-06-23 21:30 UTCEPSS rescore
  17. 2026-06-23 17:00 UTCOSV refresh
  18. 2026-06-21 01:57 UTCEPSS rescore
  19. 2026-06-21 01:57 UTCEPSS rescore
  20. 2026-06-18 17:50 UTCEPSS rescore
  21. 2026-06-17 17:50 UTCEPSS rescore
  22. 2026-06-17 17:49 UTCEPSS rescore
  23. 2026-06-16 17:50 UTCEPSS rescore
  24. 2026-06-16 17:50 UTCEPSS rescore
  25. 2026-06-15 17:45 UTCEPSS rescore
  26. 2026-06-14 23:14 UTCEPSS rescore
  27. 2026-06-13 22:57 UTCEPSS rescore
  28. 2026-06-12 23:09 UTCEPSS rescore
  29. 2026-06-12 23:09 UTCEPSS rescore
  30. 2026-06-10 22:15 UTCEPSS rescore
  31. 2026-06-07 15:22 UTCEPSS rescore
  32. 2026-06-06 22:59 UTCOSV refresh
  33. 2026-06-06 13:45 UTCEPSS rescore
  34. 2026-06-05 06:08 UTCEPSS rescore
  35. 2026-06-05 06:08 UTCEPSS rescore
  36. 2026-06-04 13:10 UTCEPSS rescore
  37. 2026-06-04 13:10 UTCEPSS rescore
  38. 2026-06-02 20:10 UTCEPSS rescore
  39. 2026-06-01 13:49 UTCEPSS rescore
  40. 2026-06-01 13:49 UTCEPSS rescore
  41. 2026-05-31 22:28 UTCEPSS rescore
  42. 2026-05-31 22:28 UTCEPSS rescore
  43. 2026-05-31 00:14 UTCEPSS rescore
  44. 2026-05-29 13:41 UTCEPSS rescore
  45. 2026-05-27 13:38 UTCEPSS rescore
  46. 2026-05-27 13:38 UTCEPSS rescore
  47. 2026-05-26 07:16 UTCEPSS rescore
  48. 2026-05-26 07:16 UTCEPSS rescore
  49. 2026-05-22 21:23 UTCEG score recompute
  50. 2026-05-22 21:23 UTCVendor advisory
  51. 2026-05-22 21:23 UTCGHSA enrichment
  52. 2026-05-22 21:15 UTCEPSS rescore
  53. 2026-05-20 22:37 UTCEPSS rescore
  54. 2026-05-20 22:37 UTCEPSS rescore
  55. 2026-05-20 11:21 UTCEPSS rescore
  56. 2026-05-20 11:21 UTCEPSS rescore
  57. 2026-05-20 11:21 UTCEPSS rescore
  58. 2026-05-18 21:30 UTCEPSS rescore
  59. 2026-05-18 21:30 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2016-0742?
CVE-2016-0742 is a high vulnerability published on February 15, 2016. The resolver in nginx before 1.8.1 and 1.9.x before 1.9.10 allows remote attackers to cause a denial of service (invalid pointer dereference and worker process crash) via a crafted UDP DNS response.
When was CVE-2016-0742 disclosed?
CVE-2016-0742 was first published in the National Vulnerability Database on February 15, 2016, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-0742 actively exploited?
CVE-2016-0742 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 82% probability of exploitation in the next 30 days, which ranks it in the top 0.4% of all scored CVEs.
What is the CVSS score of CVE-2016-0742?
CVE-2016-0742 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.9.
How do I remediate CVE-2016-0742?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-0742, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2016-0742

Explore →

Is Your Infrastructure Affected by CVE-2016-0742?

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

Start Free Scan →Browse All CVEs