CVE-2017-1000248

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 2.0%, top 22% 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
Trending — 3 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 9.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Redis-store <=v1.3.0 allows unsafe objects to be loaded from redis

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity98% × 45%
Exploitation2% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
2%
EPSS %ILE
78%
KEV
Not listed

Published

November 17, 2017

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Jul 26, 2026
Patch available. Sources: github_commit.
github_commit Patch Available

commit e0c1398d54a9 (redis-store/redis-store)

Patch available: redis-store/redis-store v1.4.0 (contains commit e0c1398d54a9)

https://github.com/redis-store/redis-store/commit/e0c1398d54a9661c8c70267c3a925ba6b192142e

Affected Packages

(1 across 1 ecosystem)
RubyGems(1)
PackageVulnerable rangeFixed inDependents
redis-store0.3.6 ... 1.3.0 (24 versions)1.4.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 43× 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 103 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2017-1000248?
CVE-2017-1000248 is a critical vulnerability published on November 17, 2017. Redis-store <=v1.3.0 allows unsafe objects to be loaded from redis
When was CVE-2017-1000248 disclosed?
CVE-2017-1000248 was first published in the National Vulnerability Database on November 17, 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-1000248 actively exploited?
CVE-2017-1000248 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 21.5% of all scored CVEs.
What is the CVSS score of CVE-2017-1000248?
CVE-2017-1000248 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-1000248?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-1000248, 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-1000248

Explore →

Is Your Infrastructure Affected by CVE-2017-1000248?

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

Start Free Scan →Browse All CVEs