CVE-2018-0016

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 4.1% (90th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 7.5 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2022-05-13) is not newer than that change (2024-11-21), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2018-0841 (ENISA EUVD) · GHSA-mgmx-337f-xc42 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 4.1%CVSS: 9.8Exploit: None knownExposed services: Not assessed

The following software releases have been updated to resolve this specific issue: 15.1F5-S3, 15.1F6-S8, 15.1F7, 15.1R5, 15.1X49-D60, 15.1X53-D66, 15.1X53-D233, 15.1X53-D471, 16.1R1, and all subsequent releases (from the CVE record's solution, Juniper Networks, Inc.) — apply it.

Receipt of a specially crafted Connectionless Network Protocol (CLNP) datagram destined to an interface of a Junos OS device may result in a kernel crash or lead to remote code execution. Devices are only vulnerable to the specially crafted CLNP datagram if 'clns-routing' or ES-IS is explicitly configured. Devices with without CLNS enabled are not vulnerable to this issue. Devices with IS-IS configured on the interface are not vulnerable to this issue unless CLNS routing is also enabled. This issue only affects devices running Junos OS 15.1. Affected releases are Juniper Networks Junos OS: 15.1 versions prior to 15.1F5-S3, 15.1F6-S8, 15.1F7, 15.1R5; 15.1X49 versions prior to 15.1X49-D60; 15.1X53 versions prior to 15.1X53-D66, 15.1X53-D233, 15.1X53-D471. Earlier releases are unaffected by this vulnerability, and the issue has been resolved in Junos OS 16.1R1 and all subsequent releases.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
46
EG Risk 46/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation4.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The following software releases have been updated to resolve this specific issue: 15.1F5-S3, 15.1F6-S8, 15.1F7, 15.1R5, 15.1X49-D60, 15.1X53-D66, 15.1X53-D233, 15.1X53-D471, 16.1R1, and all subsequent releases (from the CVE record's solution, Juniper Networks, Inc.). Apply it within your standard update timelines.
EPSS PROB
4.1%
EPSS %ILE
90th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
4.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

The following software releases have been updated to resolve this specific issue: 15.1F5-S3, 15.1F6-S8, 15.1F7, 15.1R5, 15.1X49-D60, 15.1X53-D66, 15.1X53-D233, 15.1X53-D471, 16.1R1, and all subsequent releases (from the CVE record's solution, Juniper Networks, Inc.). Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 11, 2018

Last Modified

November 21, 2024

Advisory Details (3)

Auto-updated Oct 7, 2026
Fix named in the CVE record's solution (Juniper Networks, Inc.).

Data Freshness Timeline

(refreshed 13× in last 7d / 58× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 259 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 159 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-22 08:03 UTCEchelonGraph re-scored
  2. 2026-11-22 08:03 UTCGHSA enrichmentGHSA-mgmx-337f-xc42 · GitHub severity HIGH · GitHub CVSS 7.5
  3. 2026-11-21 16:29 UTCEPSS rescoreEPSS 4.1% · 90th percentile
  4. 2026-11-21 08:40 UTCEchelonGraph re-scored
  5. 2026-11-21 08:40 UTCGHSA enrichmentGHSA-mgmx-337f-xc42 · GitHub severity HIGH · GitHub CVSS 7.5
  6. 2026-11-20 16:29 UTCEPSS rescoreEPSS 4.1% · 90th percentile
  7. 2026-11-20 09:18 UTCEchelonGraph re-scored
  8. 2026-11-20 09:18 UTCGHSA enrichmentGHSA-mgmx-337f-xc42 · GitHub severity HIGH · GitHub CVSS 7.5
  9. 2026-11-19 16:27 UTCEPSS rescoreEPSS 4.1% · 90th percentile
  10. 2026-11-19 09:57 UTCEchelonGraph re-scored
  11. 2026-11-19 09:57 UTCGHSA enrichmentGHSA-mgmx-337f-xc42 · GitHub severity HIGH · GitHub CVSS 7.5
  12. 2026-11-18 16:28 UTCEPSS rescoreEPSS 4.1% · 90th percentile
  13. 2026-11-18 10:34 UTCEchelonGraph re-scored
  14. 2026-11-18 10:34 UTCGHSA enrichmentGHSA-mgmx-337f-xc42 · GitHub severity HIGH · GitHub CVSS 7.5
  15. 2026-11-17 16:29 UTCEPSS rescoreEPSS 4.1% · 90th percentile
  16. 2026-11-17 11:12 UTCEchelonGraph re-scored
  17. 2026-11-17 11:12 UTCGHSA enrichmentGHSA-mgmx-337f-xc42 · GitHub severity HIGH · GitHub CVSS 7.5
  18. 2026-11-16 16:35 UTCEPSS rescoreEPSS 4.1% · 90th percentile
  19. 2026-11-16 11:50 UTCEchelonGraph re-scored
  20. 2026-11-16 11:50 UTCGHSA enrichmentGHSA-mgmx-337f-xc42 · GitHub severity HIGH · GitHub CVSS 7.5
  21. 2026-11-15 16:36 UTCEPSS rescoreEPSS 4.1% · 90th percentile
  22. 2026-11-15 12:24 UTCEchelonGraph re-scored
  23. 2026-11-15 12:24 UTCGHSA enrichmentGHSA-mgmx-337f-xc42 · GitHub severity HIGH · GitHub CVSS 7.5
  24. 2026-11-14 16:31 UTCEPSS rescoreEPSS 4.1% · 90th percentile
  25. 2026-11-14 13:01 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-11-14 13:01 UTCGHSA enrichmentGHSA-mgmx-337f-xc42 · GitHub severity HIGH · GitHub CVSS 7.5
  2. 2026-11-13 16:37 UTCEPSS rescoreEPSS 4.1% · 90th percentile
  3. 2026-11-13 13:38 UTCEchelonGraph re-scored
  4. 2026-11-13 13:38 UTCGHSA enrichmentGHSA-mgmx-337f-xc42 · GitHub severity HIGH · GitHub CVSS 7.5
  5. 2026-11-12 16:28 UTCEPSS rescoreEPSS 4.1% · 90th percentile
  6. 2026-11-12 14:16 UTCEchelonGraph re-scored
  7. 2026-11-12 14:16 UTCGHSA enrichmentGHSA-mgmx-337f-xc42 · GitHub severity HIGH · GitHub CVSS 7.5
  8. 2026-11-11 16:29 UTCEPSS rescoreEPSS 4.1% · 90th percentile
  9. 2026-11-11 14:53 UTCEchelonGraph re-scored
  10. 2026-11-11 14:53 UTCGHSA enrichmentGHSA-mgmx-337f-xc42 · GitHub severity HIGH · GitHub CVSS 7.5
  11. 2026-11-10 16:31 UTCEPSS rescoreEPSS 4.1% · 90th percentile
  12. 2026-11-10 15:31 UTCEchelonGraph re-scored
  13. 2026-11-10 15:31 UTCGHSA enrichmentGHSA-mgmx-337f-xc42 · GitHub severity HIGH · GitHub CVSS 7.5
  14. 2026-11-09 16:27 UTCEPSS rescoreEPSS 4.1% · 90th percentile
  15. 2026-11-09 16:08 UTCGHSA enrichmentGHSA-mgmx-337f-xc42 · GitHub severity HIGH · GitHub CVSS 7.5
  16. 2026-11-08 16:43 UTCEchelonGraph re-scored
  17. 2026-11-08 16:43 UTCGHSA enrichmentGHSA-mgmx-337f-xc42 · GitHub severity HIGH · GitHub CVSS 7.5
  18. 2026-11-08 16:30 UTCEPSS rescoreEPSS 4.1% · 90th percentile
  19. 2026-11-07 17:19 UTCEchelonGraph re-scored
  20. 2026-11-07 17:19 UTCGHSA enrichmentGHSA-mgmx-337f-xc42 · GitHub severity HIGH · GitHub CVSS 7.5
  21. 2026-11-07 16:31 UTCEPSS rescoreEPSS 4.1% · 90th percentile
  22. 2026-11-06 17:57 UTCEchelonGraph re-scored
  23. 2026-11-06 17:57 UTCGHSA enrichmentGHSA-mgmx-337f-xc42 · GitHub severity HIGH · GitHub CVSS 7.5
  24. 2026-11-06 16:28 UTCEPSS rescoreEPSS 4.1% · 90th percentile
  25. 2026-11-05 18:35 UTCEchelonGraph re-scored
  26. 2026-11-05 18:35 UTCGHSA enrichmentGHSA-mgmx-337f-xc42 · GitHub severity HIGH · GitHub CVSS 7.5
  27. 2026-11-05 16:28 UTCEPSS rescoreEPSS 4.1% · 90th percentile
  28. 2026-11-04 19:13 UTCEchelonGraph re-scored
  29. 2026-11-04 19:13 UTCGHSA enrichmentGHSA-mgmx-337f-xc42 · GitHub severity HIGH · GitHub CVSS 7.5
  30. 2026-11-04 16:28 UTCEPSS rescoreEPSS 4.1% · 90th percentile
  31. 2026-11-03 19:51 UTCEchelonGraph re-scored
  32. 2026-11-03 19:51 UTCGHSA enrichmentGHSA-mgmx-337f-xc42 · GitHub severity HIGH · GitHub CVSS 7.5
  33. 2026-11-03 16:34 UTCEPSS rescoreEPSS 4.1% · 90th percentile
  34. 2026-11-02 20:29 UTCEchelonGraph re-scored
  35. 2026-11-02 20:29 UTCGHSA enrichmentGHSA-mgmx-337f-xc42 · GitHub severity HIGH · GitHub CVSS 7.5
  36. 2026-11-01 21:05 UTCEchelonGraph re-scored
  37. 2026-11-01 21:05 UTCGHSA enrichmentGHSA-mgmx-337f-xc42 · GitHub severity HIGH · GitHub CVSS 7.5
  38. 2026-10-31 21:42 UTCEchelonGraph re-scored
  39. 2026-10-31 21:42 UTCGHSA enrichmentGHSA-mgmx-337f-xc42 · GitHub severity HIGH · GitHub CVSS 7.5
  40. 2026-10-31 16:27 UTCEPSS rescoreEPSS 4.1% · 90th percentile
  41. 2026-10-30 22:21 UTCEchelonGraph re-scored
  42. 2026-10-30 22:21 UTCGHSA enrichmentGHSA-mgmx-337f-xc42 · GitHub severity HIGH · GitHub CVSS 7.5
  43. 2026-10-30 16:28 UTCEPSS rescoreEPSS 4.1% · 90th percentile
  44. 2026-10-29 22:58 UTCEchelonGraph re-scored
  45. 2026-10-29 22:58 UTCGHSA enrichmentGHSA-mgmx-337f-xc42 · GitHub severity HIGH · GitHub CVSS 7.5
  46. 2026-10-29 16:28 UTCEPSS rescoreEPSS 4.1% · 90th percentile
  47. 2026-10-28 23:36 UTCEchelonGraph re-scored
  48. 2026-10-28 23:36 UTCGHSA enrichmentGHSA-mgmx-337f-xc42 · GitHub severity HIGH · GitHub CVSS 7.5
  49. 2026-10-28 16:27 UTCEPSS rescoreEPSS 4.1% · 90th percentile
  50. 2026-10-28 00:15 UTCEchelonGraph re-scored
  51. 2026-10-28 00:15 UTCGHSA enrichmentGHSA-mgmx-337f-xc42 · GitHub severity HIGH · GitHub CVSS 7.5
  52. 2026-10-27 16:27 UTCEPSS rescoreEPSS 4.1% · 90th percentile
  53. 2026-10-27 00:51 UTCEchelonGraph re-scored
  54. 2026-10-27 00:51 UTCGHSA enrichmentGHSA-mgmx-337f-xc42 · GitHub severity HIGH · GitHub CVSS 7.5
  55. 2026-10-26 16:26 UTCEPSS rescoreEPSS 4.1% · 90th percentile
  56. 2026-10-25 21:46 UTCGHSA enrichmentGHSA-mgmx-337f-xc42 · GitHub severity HIGH · GitHub CVSS 7.5
  57. 2026-10-25 19:28 UTCEchelonGraph re-scored
  58. 2026-10-25 16:27 UTCEPSS rescoreEPSS 4.1% · 90th percentile
  59. 2026-10-24 22:17 UTCEchelonGraph re-scored
  60. 2026-10-24 22:17 UTCGHSA enrichmentGHSA-mgmx-337f-xc42 · GitHub severity HIGH · GitHub CVSS 7.5
  61. 2026-10-24 16:27 UTCEPSS rescoreEPSS 4.1% · 90th percentile
  62. 2026-10-23 22:56 UTCEchelonGraph re-scored
  63. 2026-10-23 22:56 UTCGHSA enrichmentGHSA-mgmx-337f-xc42 · GitHub severity HIGH · GitHub CVSS 7.5
  64. 2026-10-23 16:27 UTCEPSS rescoreEPSS 4.1% · 90th percentile
  65. 2026-10-22 23:20 UTCEchelonGraph re-scored
  66. 2026-10-22 23:20 UTCGHSA enrichmentGHSA-mgmx-337f-xc42 · GitHub severity HIGH · GitHub CVSS 7.5
  67. 2026-10-22 16:27 UTCEPSS rescoreEPSS 4.1% · 90th percentile
  68. 2026-10-21 23:56 UTCEchelonGraph re-scored
  69. 2026-10-21 23:56 UTCGHSA enrichmentGHSA-mgmx-337f-xc42 · GitHub severity HIGH · GitHub CVSS 7.5
  70. 2026-10-21 16:27 UTCEPSS rescoreEPSS 4.1% · 90th percentile
  71. 2026-10-20 16:27 UTCEPSS rescoreEPSS 4.1% · 90th percentile
  72. 2026-10-19 16:26 UTCEPSS rescoreEPSS 4.1% · 90th percentile
  73. 2026-10-18 16:27 UTCEPSS rescoreEPSS 4.1% · 90th percentile
  74. 2026-10-18 10:25 UTCEchelonGraph re-scored
  75. 2026-10-17 16:27 UTCEPSS rescoreEPSS 4.1% · 90th percentile

Frequently asked(5)

What is CVE-2018-0016?
CVE-2018-0016 is a critical-severity vulnerability; its CVE record was published on April 11, 2018. Receipt of a specially crafted Connectionless Network Protocol (CLNP) datagram destined to an interface of a Junos OS device may result in a kernel crash or lead to remote code execution. Devices are only vulnerable to the specially crafted CLNP datagram if 'clns-routing' or ES-IS is explicitly…
When was CVE-2018-0016 made public?
CVE-2018-0016 was made public on April 11, 2018: that is the date its CVE record's CNA, Juniper Networks, Inc., gives for when the vulnerability was made public. The CVE record itself was published on April 11, 2018. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2018-0016 actively exploited?
CVE-2018-0016 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.1% probability of exploitation in the next 30 days (90th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2018-0016?
CVE-2018-0016 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2018-0016?
The CVE record's solution for CVE-2018-0016, written by its CNA Juniper Networks, Inc., names the fix: "The following software releases have been updated to resolve this specific issue: 15.1F5-S3, 15.1F6-S8, 15.1F7, 15.1R5, 15.1X49-D60, 15.1X53-D66, 15.1X53-D233, 15.1X53-D471, 16.1R1, and all subsequent releases."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2018-0016

Explore →

Is Your Infrastructure Affected by CVE-2018-0016?

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