CVE-2025-14265

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2025-12-11. NVD baseline CVSS 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2025-202687 (ENISA EUVD) · GHSA-3hj4-mq9q-jpmj (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
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: 0.4%CVSS: 9.1Exploit: None knownExposed services: Not assessed

On-prem: * ScreenConnect Partners: Please upgrade to ScreenConnect version 25.8 and update your guest clients to the same version (from the CVE record's solution, ConnectWise LLC) — apply it.

In versions of ScreenConnect™ prior to 25.8, server-side validation and integrity checks within the extension subsystem could allow the installation and execution of untrusted or arbitrary extensions by authorized or administrative users. Abuse of this behavior could result in the execution of custom code on the server or unauthorized access to application configuration data. This issue affects only the ScreenConnect server component; host and guest clients are not impacted. ScreenConnect 25.8 introduces enhanced server-side configuration handling and integrity checks to ensure only trusted extensions can be installed.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
41
EG Risk 41/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)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 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: On-prem: * ScreenConnect Partners: Please upgrade to ScreenConnect version 25.8 and update your guest clients to the same version (from the CVE record's solution, ConnectWise LLC). Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
30th
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.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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).

On-prem: * ScreenConnect Partners: Please upgrade to ScreenConnect version 25.8 and update your guest clients to the same version (from the CVE record's solution, ConnectWise LLC). Apply it within your standard update timelines.

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.

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

December 11, 2025

Last Modified

October 7, 2026

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 21× 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 226 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 128 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-14265?
CVE-2025-14265 is a critical-severity vulnerability; its CVE record was published on December 11, 2025. In versions of ScreenConnect™ prior to 25.8, server-side validation and integrity checks within the extension subsystem could allow the installation and execution of untrusted or arbitrary extensions by authorized or administrative users. Abuse of this behavior could result in the execution of…
When was the CVE record for CVE-2025-14265 published?
The CVE record for CVE-2025-14265 was published on December 11, 2025. 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 7, 2026; the record at its source may have been updated since.
Is CVE-2025-14265 actively exploited?
CVE-2025-14265 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-14265?
CVE-2025-14265 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2025-14265?
The CVE record's solution for CVE-2025-14265, written by its CNA ConnectWise LLC, names the fix: "On-prem: * ScreenConnect Partners: Please upgrade to ScreenConnect version 25.8 and update your guest clients to the same version."

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-14265?

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