CVE-2025-34101

CRITICALNVD 9.39.3
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.3 under NVD CVSS v3. EPSS exploit probability: 4.4% (91st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this weekWeaponized

Also known asEUVD-2025-21036 (ENISA EUVD) · GHSA-4q44-m9gw-jvmm (GitHub Security Advisories)Source: ENISA EUVD

9.3EG
EchelonGraph verdictPlan mitigationNo fix is confirmed yet: check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule (the SSVC decision on this page).
  • Public exploit code is available (Metasploit)
CISA-KEV: Not listedEPSS PROB: 4.4%CVSS: 9.3Exploit: MetasploitExposed services: Not assessed

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

The CVE record's CNA (VulnCheck) lists Serviio Media Server versions 1.4 up to and including 1.8 as affected. No release containing a fix is confirmed on record.

An unauthenticated command injection vulnerability exists in Serviio Media Server versions 1.4 through 1.8 on Windows, in the /rest/action API endpoint exposed by the console component (default port 23423). The checkStreamUrl method accepts a VIDEO parameter that is passed unsanitized to a call to cmd.exe, enabling arbitrary command execution under the privileges of the web server. No authentication is required to exploit this issue, as the REST API is exposed by default and lacks access controls.

CVSS v3
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
68
EG Risk 68/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)
Severity93% × 45%
Impact severity (EG Severity): CVSS 9.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation65% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 2 (Weaponized): a constant, not a probability.
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. Check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule.
EPSS PROB
4.4%
EPSS %ILE
91st
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.3): severity, escalated by confirmed exploitation. This CVE's 9.3 is its impact severity (EG Severity), not escalated.

EG Severity
9.3 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.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.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).

No fix is confirmed yet. Check with the vendor for a fixed release; until one is applied, restrict network exposure of the affected system on your normal schedule.

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.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

The score's inputs: 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

July 10, 2025

Last Modified

April 15, 2026

Advisory Details (6)

Auto-updated Sep 15, 2026
No fix on record yet.
Web page

Zero Science Lab — Information Security Research & Development Laboratory

https://www.zeroscience.mk/en/vulnerabilities/ZSL-2017-5408.php
Web page

Serviio Media Server - checkStreamUrl Command Execution (Metasploit) - Windows remote Exploit

https://www.exploit-db.com/exploits/42023
Web page

Serviio Media Server Unauthenticated Command Injection via checkStreamUrl VIDEO Parameter | Advisories | VulnCheck

https://vulncheck.com/advisories/serviio-media-server-unauthenticated-command-injection
Web page

Locked Out | Packet Storm

https://packetstorm.news/files/id/142387

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 67× 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 99 of 225 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 126 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 Metasploit module). No fix is confirmed yet, so defenders should restrict or isolate affected systems accordingly until one is published.

  • Metasploitexploit/windows/http/serviio_checkstreamurl_cmd_exec✓ verified
    Published May 16, 2017

    Serviio Media Server checkStreamUrl Command Execution

    Open source ↗

Frequently asked(5)

What is CVE-2025-34101?
CVE-2025-34101 is a critical-severity vulnerability; its CVE record was published on July 10, 2025. An unauthenticated command injection vulnerability exists in Serviio Media Server versions 1.4 through 1.8 on Windows, in the /rest/action API endpoint exposed by the console component (default port 23423). The checkStreamUrl method accepts a VIDEO parameter that is passed unsanitized to a call to…
When was CVE-2025-34101 made public?
CVE-2025-34101 was made public on May 17, 2017: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on July 10, 2025. EchelonGraph's copy of the record carries a last-modified date of April 15, 2026; the record at its source may have been updated since.
Is CVE-2025-34101 actively exploited?
CVE-2025-34101 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: a Metasploit module exists for it. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 4.4% probability of exploitation in the next 30 days (91st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-34101?
CVE-2025-34101 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2025-34101?
No fix for CVE-2025-34101 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix. The CVE record's CNA (VulnCheck) lists Serviio Media Server versions 1.4 up to and including 1.8 as affected. No release containing a fix is confirmed on record.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-34101?

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