CVE-2025-61765

MEDIUMPre-NVD 6.46.4
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (41st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2025-32096 (ENISA EUVD)Source: ENISA EUVD

6.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

python-socketio is a Python implementation of the Socket.IO realtime client and server. A remote code execution vulnerability in python-socketio versions prior to 5.14.0 allows attackers to execute arbitrary Python code through malicious pickle deserialization in multi-server deployments on which the attacker previously gained access to the message queue that the servers use for internal communications. When Socket.IO servers are configured to use a message queue backend such as Redis for inter-server communication, messages sent between the servers are encoded using the pickle Python module. When a server receives one of these messages through the message queue, it assumes it is trusted and immediately deserializes it. The vulnerability stems from deserialization of messages using Python's pickle.loads() function. Having previously obtained access to the message queue, the attacker can send a python-socketio server a crafted pickle payload that executes arbitrary code during deserialization via Python's __reduce__ method. This vulnerability only affects deployments with a compromised message queue. The attack can lead to the attacker executing random code in the context of, and with the privileges of a Socket.IO server process. Single-server systems that do not use a message queue, and multi-server systems with a secure message queue are not vulnerable. In addition to making sure standard security practices are followed in the deployment of the message queue, users of the python-socketio package can upgrade to version 5.14.0 or newer, which remove the pickle module and use the much safer JSON encoding for inter-server messaging.

CVSS v3
6.4
EG Score
6.4MEDIUMmedium confidence
EG Risk
29
EG Risk 29/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)
Severity64% × 45%
Impact severity (EG Severity): CVSS 6.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
41st
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 (6.4): severity, escalated by confirmed exploitation. This CVE's 6.4 is its impact severity (EG Severity), not escalated.

EG Severity
6.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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).

A fix is available. 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.

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

October 6, 2025

Last Modified

October 9, 2026

Advisory Details (3)

Auto-updated Oct 9, 2026
Patch available. Sources: github_commit, github.
Web page

CVE-2025-61765 RCE in Socket.IO Ecosystem — BlueRock Security

https://www.bluerock.io/post/cve-2025-61765-bluerock-discovers-critical-rce-in-socket-io-ecosystem
GitHub advisoryMentions a patch (unverified)

Arbitrary Python code execution (RCE) through malicious pickle deserialization in certain multi-server deployments · Advisory · miguelgrinberg/python-socketio · GitHub

https://github.com/miguelgrinberg/python-socketio/security/advisories/GHSA-g8c6-8fjj-2r4m
GitHub commit Patch Available

commit 53f6be094257 (miguelgrinberg/python-socketio)

Patch available: miguelgrinberg/python-socketio v5.14.0 (contains commit 53f6be094257)

https://github.com/miguelgrinberg/python-socketio/commit/53f6be094257ed81476b0e212c8cddd6d06ca39a

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
python-socketio5.0.3-2 ... 5.7.2-2 (8 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
python-socketio5.11.2-1 ... 5.7.2-2 (7 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-socketio5.12.1-1, 5.13.0-1, 5.16.0-1, 5.17.0-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
python-socketio5.12.1-1, 5.13.0-1
  • every version up to 5.16.0-1: fixed in 5.16.0-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
python-socketio0.8.0 ... 5.9.0 (87 versions)
  • 0.8.0 up to 5.14.0: fixed in 5.14.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 38× 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 95 of 216 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. 5 repeat rows among the latest 100 are merged into the row they repeat. The 121 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Same product

1 shown

Debian:12:python-socketio

Frequently asked(5)

What is CVE-2025-61765?
CVE-2025-61765 is a medium-severity vulnerability; its CVE record was published on October 6, 2025. python-socketio is a Python implementation of the Socket.IO realtime client and server. A remote code execution vulnerability in python-socketio versions prior to 5.14.0 allows attackers to execute arbitrary Python code through malicious pickle deserialization in multi-server deployments on which…
When was the CVE record for CVE-2025-61765 published?
The CVE record for CVE-2025-61765 was published on October 6, 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 9, 2026; the record at its source may have been updated since.
Is CVE-2025-61765 actively exploited?
CVE-2025-61765 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-61765?
CVE-2025-61765 has a CVSS base score of 6.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-61765?
A fix for CVE-2025-61765 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-61765

Explore →

Is Your Infrastructure Affected by CVE-2025-61765?

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

Book a Demo →Browse All CVEs