CVE-2025-46418

HIGHPre-NVD 7.67.6
EchelonGraph scoreMEDIUM confidence

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

Score 7.6 from GitHub Security Advisory (severity: HIGH) published 2026-09-02. A secondary CVSS source baseline 7.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2025-210821 (ENISA EUVD) · GHSA-2hx8-j556-mj7h (GitHub Security Advisories)Source: ENISA EUVD

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

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

Westermo WeOS 5.x starting from 5.24 allows OS command injection via a media definition.

CVSS v3
7.6
EG Score
7.6HIGHmedium confidence
EG Risk
34
EG Risk 34/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)
Severity76% × 45%
Impact severity (EG Severity): CVSS 7.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.7%
EPSS %ILE
54th
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 (7.6): severity, escalated by confirmed exploitation. This CVE's 7.6 is its impact severity (EG Severity), not escalated.

EG Severity
7.6 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS. 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: 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).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (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.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). 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

September 2, 2026

Last Modified

October 19, 2026

Advisory Details (1)

Auto-updated Sep 2, 2026
No fix on record yet. Sources: cisa.
CISA

Westermo Network Technologies WeOS 5 | CISA

https://www.cisa.gov/news-events/ics-advisories/icsa-25-261-01

Vendor Advisories for CVE-2025-46418(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 73× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 98 of 173 refreshes 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 75 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-46418?
CVE-2025-46418 is a high-severity vulnerability; its CVE record was published on September 2, 2026. Westermo WeOS 5.x starting from 5.24 allows OS command injection via a media definition.
When was the CVE record for CVE-2025-46418 published?
The CVE record for CVE-2025-46418 was published on September 2, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 19, 2026; the record at its source may have been updated since.
Is CVE-2025-46418 actively exploited?
CVE-2025-46418 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-46418?
CVE-2025-46418 has a CVSS base score of 7.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-46418?
No fix for CVE-2025-46418 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2025-46418 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-46418

Explore →

Is Your Infrastructure Affected by CVE-2025-46418?

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