CVE-2016-4921

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2022-05-13. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 3%CVSS: 7.5Exploit: NoneExposed: 0

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

By flooding a Juniper Networks router running Junos OS with specially crafted IPv6 traffic, all available resources can be consumed, leading to the inability to store next hop information for legitimate traffic. In extreme cases, the crafted IPv6 traffic may result in a total resource exhaustion and kernel panic. The issue is triggered by traffic destined to the router. Transit traffic does not trigger the vulnerability. This issue only affects devices with IPv6 enabled and configured. Devices not configured to process IPv6 traffic are unaffected by this vulnerability. This issue was found during internal product security testing. Juniper SIRT is not aware of any malicious exploitation of this vulnerability. Affected releases are Juniper Networks Junos OS 11.4 prior to 11.4R13-S3; 12.3 prior to 12.3R3-S4; 12.3X48 prior to 12.3X48-D30; 13.3 prior to 13.3R10, 13.3R4-S11; 14.1 prior to 14.1R2-S8, 14.1R4-S12, 14.1R8; 14.1X53 prior to 14.1X53-D28, 14.1X53-D40; 14.1X55 prior to 14.1X55-D35; 14.2 prior to 14.2R3-S10, 14.2R4-S7, 14.2R6; 15.1 prior to 15.1F2-S5, 15.1F5-S2, 15.1F6, 15.1R3; 15.1X49 prior to 15.1X49-D40; 15.1X53 prior to 15.1X53-D57, 15.1X53-D70.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
85.3%
KEV
Not listed

Published

October 13, 2017

Last Modified

May 13, 2026

References (6)

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2016-4921?
CVE-2016-4921 is a high vulnerability published on October 13, 2017. By flooding a Juniper Networks router running Junos OS with specially crafted IPv6 traffic, all available resources can be consumed, leading to the inability to store next hop information for legitimate traffic. In extreme cases, the crafted IPv6 traffic may result in a total resource exhaustion…
When was CVE-2016-4921 disclosed?
CVE-2016-4921 was first published in the National Vulnerability Database on October 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-2016-4921 actively exploited?
CVE-2016-4921 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 85.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2016-4921?
CVE-2016-4921 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2016-4921?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-4921, 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-2016-4921

Explore →

Is Your Infrastructure Affected by CVE-2016-4921?

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

Start Free Scan →Browse All CVEs