CVE-2017-16516

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 3.8%, top 11% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 4%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

In the yajl-ruby gem 1.3.0 for Ruby, when a crafted JSON file is supplied to Yajl::Parser.new.parse, the whole ruby process crashes with a SIGABRT in the yajl_string_decode function in yajl_encode.c. This results in the whole ruby process terminating and potentially a denial of service.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity75% × 45%
Exploitation4% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
4%
EPSS %ILE
89%
KEV
Not listed

Published

November 3, 2017

Last Modified

June 17, 2026

References (10)

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuyajl-tools (2.1.0-3ubuntu0.23.04.1) @ lunar2026-05-22ubuntu
ubuntulibyajl2 (2.1.0-2ubuntu0.16.04.1~esm1) @ xenial2026-05-22ubuntu

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

(19 across 7 ecosystems)
Debian:11(4)
PackageVulnerable rangeFixed inDependents
burp2.2.18-8 ... 3.1.4-5 (7 versions)——
r-cran-jsonlite1.7.2+dfsg-1 ... 2.0.0+dfsg-2 (13 versions)——
ruby-yajl—1.2.0-3.1—
yajl2.1.0-3, 2.1.0-3+deb11u12.1.0-3+deb11u2—
Debian:12(4)
PackageVulnerable rangeFixed inDependents
burp3.1.4-1, 3.1.4-3, 3.1.4-3.1, 3.1.4-4, 3.1.4-5——
r-cran-jsonlite1.8.4+dfsg-1 ... 2.0.0+dfsg-2 (8 versions)——
ruby-yajl—1.2.0-3.1—
yajl2.1.0-3, 2.1.0-3+deb12u12.1.0-3+deb12u2—
Debian:13(4)
PackageVulnerable rangeFixed inDependents
burp—3.1.4-2—
r-cran-jsonlite—1.8.8+dfsg-1—
ruby-yajl—1.2.0-3.1—
yajl—2.1.0-4—
Debian:14(3)
PackageVulnerable rangeFixed inDependents
r-cran-jsonlite—1.8.8+dfsg-1—
ruby-yajl—1.2.0-3.1—
yajl—2.1.0-4—
Debian:10(2)
PackageVulnerable rangeFixed inDependents
burp2.1.32-22.1.32-2+deb10u1—
yajl2.1.0-3, 2.1.0-3+deb10u12.1.0-3+deb10u2—
Debian:7(1)
PackageVulnerable rangeFixed inDependents
ruby-yajl1.1.0-21.1.0-2+deb7u1—
RubyGems(1)
PackageVulnerable rangeFixed inDependents
yajl-ruby0.5.10 ... 1.3.0 (39 versions)1.3.1—

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 5× in last 7d / 24× 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 134 total refreshes for this CVE.

  1. 2026-09-07 15:56 UTCEPSS rescore
  2. 2026-09-04 13:56 UTCEPSS rescore
  3. 2026-09-04 05:01 UTCEPSS rescore
  4. 2026-09-02 14:07 UTCEPSS rescore
  5. 2026-09-01 13:48 UTCEPSS rescore
  6. 2026-09-01 03:31 UTCEPSS rescore
  7. 2026-08-30 19:13 UTCEPSS rescore
  8. 2026-08-30 04:48 UTCOSV refresh
  9. 2026-08-28 21:36 UTCEPSS rescore
  10. 2026-08-27 14:20 UTCEPSS rescore
  11. 2026-08-26 14:41 UTCEPSS rescore
  12. 2026-08-25 13:44 UTCEPSS rescore
  13. 2026-08-24 14:10 UTCEPSS rescore
  14. 2026-08-21 23:44 UTCEPSS rescore
  15. 2026-08-20 22:50 UTCEPSS rescore
  16. 2026-08-19 16:59 UTCEPSS rescore
  17. 2026-08-18 13:43 UTCEPSS rescore
  18. 2026-08-17 13:42 UTCEPSS rescore
  19. 2026-08-16 14:51 UTCEPSS rescore
  20. 2026-08-16 02:10 UTCEPSS rescore
  21. 2026-08-15 01:26 UTCEPSS rescore
  22. 2026-08-13 21:56 UTCEPSS rescore
  23. 2026-08-13 17:51 UTCOSV refresh
  24. 2026-08-09 13:42 UTCEPSS rescore
  25. 2026-08-08 16:32 UTCEPSS rescore
Show 75 more
  1. 2026-08-07 16:22 UTCEPSS rescore
  2. 2026-08-06 13:42 UTCEPSS rescore
  3. 2026-08-05 19:12 UTCEPSS rescore
  4. 2026-08-04 15:05 UTCEPSS rescore
  5. 2026-08-04 10:32 UTCEPSS rescore
  6. 2026-08-03 10:30 UTCEPSS rescore
  7. 2026-08-02 02:23 UTCEPSS rescore
  8. 2026-08-01 04:11 UTCEPSS rescore
  9. 2026-07-30 16:24 UTCEPSS rescore
  10. 2026-07-30 01:26 UTCEPSS rescore
  11. 2026-07-28 22:51 UTCOSV refresh
  12. 2026-07-28 15:32 UTCEPSS rescore
  13. 2026-07-26 14:51 UTCEPSS rescore
  14. 2026-07-25 14:13 UTCEPSS rescore
  15. 2026-07-23 14:15 UTCEPSS rescore
  16. 2026-07-23 01:28 UTCEG score recompute
  17. 2026-07-22 22:07 UTCEG score recompute
  18. 2026-07-22 14:04 UTCEPSS rescore
  19. 2026-07-21 15:21 UTCEPSS rescore
  20. 2026-07-21 15:21 UTCEPSS rescore
  21. 2026-07-20 17:04 UTCEPSS rescore
  22. 2026-07-20 17:04 UTCEPSS rescore
  23. 2026-07-19 14:28 UTCEPSS rescore
  24. 2026-07-19 14:28 UTCEPSS rescore
  25. 2026-07-19 02:26 UTCEPSS rescore
  26. 2026-07-19 02:26 UTCEPSS rescore
  27. 2026-07-18 10:00 UTCEPSS rescore
  28. 2026-07-16 16:59 UTCEPSS rescore
  29. 2026-07-16 16:59 UTCEPSS rescore
  30. 2026-07-15 16:54 UTCEPSS rescore
  31. 2026-07-15 16:54 UTCEPSS rescore
  32. 2026-07-15 01:56 UTCEPSS rescore
  33. 2026-07-13 22:26 UTCEPSS rescore
  34. 2026-07-13 06:09 UTCEPSS rescore
  35. 2026-07-12 05:43 UTCEPSS rescore
  36. 2026-07-11 15:22 UTCOSV refresh
  37. 2026-07-11 08:24 UTCEPSS rescore
  38. 2026-07-09 19:06 UTCEPSS rescore
  39. 2026-07-08 15:10 UTCEPSS rescore
  40. 2026-07-07 13:42 UTCEPSS rescore
  41. 2026-07-06 16:24 UTCEPSS rescore
  42. 2026-07-06 02:20 UTCEPSS rescore
  43. 2026-07-05 02:27 UTCEPSS rescore
  44. 2026-07-04 06:28 UTCEPSS rescore
  45. 2026-07-01 15:02 UTCEPSS rescore
  46. 2026-07-01 15:02 UTCEPSS rescore
  47. 2026-06-30 23:19 UTCEPSS rescore
  48. 2026-06-30 23:19 UTCEPSS rescore
  49. 2026-06-29 14:03 UTCEPSS rescore
  50. 2026-06-28 14:04 UTCEPSS rescore
  51. 2026-06-28 04:53 UTCEPSS rescore
  52. 2026-06-27 03:05 UTCEPSS rescore
  53. 2026-06-25 13:47 UTCEPSS rescore
  54. 2026-06-25 13:47 UTCEPSS rescore
  55. 2026-06-24 14:02 UTCEPSS rescore
  56. 2026-06-23 21:30 UTCEPSS rescore
  57. 2026-06-22 22:05 UTCOSV refresh
  58. 2026-06-22 14:23 UTCEPSS rescore
  59. 2026-06-22 14:23 UTCEPSS rescore
  60. 2026-06-21 14:54 UTCEPSS rescore
  61. 2026-06-21 14:54 UTCEPSS rescore
  62. 2026-06-21 01:57 UTCEPSS rescore
  63. 2026-06-21 01:57 UTCEPSS rescore
  64. 2026-06-18 17:50 UTCEPSS rescore
  65. 2026-06-17 17:50 UTCEPSS rescore
  66. 2026-06-16 17:50 UTCEPSS rescore
  67. 2026-06-15 17:45 UTCEPSS rescore
  68. 2026-06-14 23:14 UTCEPSS rescore
  69. 2026-06-14 23:14 UTCEPSS rescore
  70. 2026-06-13 22:57 UTCEPSS rescore
  71. 2026-06-12 23:09 UTCEPSS rescore
  72. 2026-06-11 13:57 UTCEPSS rescore
  73. 2026-06-10 22:15 UTCEPSS rescore
  74. 2026-06-08 14:14 UTCEPSS rescore
  75. 2026-06-07 15:22 UTCEPSS rescore

Frequently asked(5)

What is CVE-2017-16516?
CVE-2017-16516 is a high vulnerability published on November 3, 2017. In the yajl-ruby gem 1.3.0 for Ruby, when a crafted JSON file is supplied to Yajl::Parser.new.parse, the whole ruby process crashes with a SIGABRT in the yajlstringdecode function in yajl_encode.c. This results in the whole ruby process terminating and potentially a denial of service.
When was CVE-2017-16516 disclosed?
CVE-2017-16516 was first published in the National Vulnerability Database on November 3, 2017, 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-2017-16516 actively exploited?
CVE-2017-16516 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4% probability of exploitation in the next 30 days, which ranks it in the top 10.7% of all scored CVEs.
What is the CVSS score of CVE-2017-16516?
CVE-2017-16516 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2017-16516?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-16516, 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-2017-16516

Explore →

Is Your Infrastructure Affected by CVE-2017-16516?

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

Start Free Scan →Browse All CVEs