CVE-2025-68285

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2025-12-16. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2025-203795 (ENISA EUVD) · GHSA-v24j-9ghx-7rf2 (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: 0.6%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

libceph: fix potential use-after-free in have_mon_and_osd_map()

The wait loop in __ceph_open_session() can race with the client receiving a new monmap or osdmap shortly after the initial map is received. Both ceph_monc_handle_map() and handle_one_map() install a new map immediately after freeing the old one

kfree(monc->monmap); monc->monmap = monmap;

ceph_osdmap_destroy(osdc->osdmap); osdc->osdmap = newmap;

under client->monc.mutex and client->osdc.lock respectively, but because neither is taken in have_mon_and_osd_map() it's possible for client->monc.monmap->epoch and client->osdc.osdmap->epoch arms in

client->monc.monmap && client->monc.monmap->epoch && client->osdc.osdmap && client->osdc.osdmap->epoch;

condition to dereference an already freed map. This happens to be reproducible with generic/395 and generic/397 with KASAN enabled:

BUG: KASAN: slab-use-after-free in have_mon_and_osd_map+0x56/0x70 Read of size 4 at addr ffff88811012d810 by task mount.ceph/13305 CPU: 2 UID: 0 PID: 13305 Comm: mount.ceph Not tainted 6.14.0-rc2-build2+ #1266 ... Call Trace: have_mon_and_osd_map+0x56/0x70 ceph_open_session+0x182/0x290 ceph_get_tree+0x333/0x680 vfs_get_tree+0x49/0x180 do_new_mount+0x1a3/0x2d0 path_mount+0x6dd/0x730 do_mount+0x99/0xe0 __do_sys_mount+0x141/0x180 do_syscall_64+0x9f/0x100 entry_SYSCALL_64_after_hwframe+0x76/0x7e

Allocated by task 13305: ceph_osdmap_alloc+0x16/0x130 ceph_osdc_init+0x27a/0x4c0 ceph_create_client+0x153/0x190 create_fs_client+0x50/0x2a0 ceph_get_tree+0xff/0x680 vfs_get_tree+0x49/0x180 do_new_mount+0x1a3/0x2d0 path_mount+0x6dd/0x730 do_mount+0x99/0xe0 __do_sys_mount+0x141/0x180 do_syscall_64+0x9f/0x100 entry_SYSCALL_64_after_hwframe+0x76/0x7e

Freed by task 9475: kfree+0x212/0x290 handle_one_map+0x23c/0x3b0 ceph_osdc_handle_map+0x3c9/0x590 mon_dispatch+0x655/0x6f0 ceph_con_process_message+0xc3/0xe0 ceph_con_v1_try_read+0x614/0x760 ceph_con_workfn+0x2de/0x650 process_one_work+0x486/0x7c0 process_scheduled_works+0x73/0x90 worker_thread+0x1c8/0x2a0 kthread+0x2ec/0x300 ret_from_fork+0x24/0x40 ret_from_fork_asm+0x1a/0x30

Rewrite the wait loop to check the above condition directly with client->monc.mutex and client->osdc.lock taken as appropriate. While at it, improve the timeout handling (previously mount_timeout could be exceeded in case wait_event_interruptible_timeout() slept more than once) and access client->auth_err under client->monc.mutex to match how it's set in finish_auth().

monmap_show() and osdmap_show() now take the respective lock before accessing the map as well.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
44
EG Risk 44/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.
Exploitation0.6% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.6%
EPSS %ILE
47th
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.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-30). 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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 16, 2025

Last Modified

October 14, 2026

Advisory Details (7)

Auto-updated Oct 30, 2026
Patch available.
Web page

libceph: fix potential use-after-free in have_mon_and_osd_map() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e08021b3b56b2407f37b5fe47b654be80cc665fb
Web page

libceph: fix potential use-after-free in have_mon_and_osd_map() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bb4910c5fd436701faf367e1b5476a5a6d2aff1c
Web page

libceph: fix potential use-after-free in have_mon_and_osd_map() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7c8ccdc1714d9fabecd26e1be7db1771061acc6e
Web page

libceph: fix potential use-after-free in have_mon_and_osd_map() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3fc43120b22a3d4f1fbeff56a35ce2105b6a5683
Web page

libceph: fix potential use-after-free in have_mon_and_osd_map() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/183ad6e3b651e8fb0b66d6a2678f4b80bfbba092
Web page

libceph: fix potential use-after-free in have_mon_and_osd_map() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/076381c261374c587700b3accf410bdd2dba334e
Web page

libceph: fix potential use-after-free in have_mon_and_osd_map() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/05ec43e9a9de67132dc8cd3b22afef001574947f

Vendor Advisories for CVE-2025-68285(17)

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

Patch Availability(24)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-azure-edge (5.15.0.1110.119~20.04.1) @ focal2026-10-31ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1052.58+fips1) @ noble2026-10-31ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1109.107) @ jammy2026-10-31ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1067 (5.15.0-1067.71) @ jammy2026-10-31ubuntu
redhatkernel-0:6.12.0-211.60.1.el10_22026-09-24redhat
redhatkpatch-patch2026-02-11redhat
redhatkernel-0:6.12.0-124.28.1.el10_12026-01-19redhat
redhatkernel-0:6.12.0-55.54.1.el10_02026-01-19redhat
redhatkernel-0:5.14.0-570.79.1.el9_62026-01-19redhat
redhatkernel-rt-0:3.10.0-1160.145.1.rt56.1297.el72026-01-19redhat
redhatkernel-0:5.14.0-611.24.1.el9_72026-01-19redhat
redhatkernel-0:3.10.0-1160.145.1.el72026-01-19redhat
redhatkernel-0:4.18.0-193.181.1.el8_22026-01-15redhat
redhatkernel-0:4.18.0-477.124.1.el8_82026-01-14redhat
redhatkernel-0:4.18.0-305.183.1.el8_42026-01-14redhat
redhatkernel-0:5.14.0-70.161.1.el9_02026-01-14redhat
redhatkernel-rt-0:5.14.0-284.152.1.rt14.437.el9_22026-01-14redhat
redhatkernel-0:5.14.0-284.152.1.el9_22026-01-14redhat
redhatkernel-rt-0:5.14.0-70.161.1.rt21.233.el9_02026-01-14redhat
redhatkernel-0:4.18.0-372.175.1.el8_62026-01-14redhat
redhatkernel-0:5.14.0-427.106.1.el9_42026-01-13redhat
redhatkernel-rt-0:4.18.0-553.92.1.rt7.433.el8_102026-01-12redhat
redhatkernel-0:4.18.0-553.92.1.el8_102026-01-12redhat
linuxKernel @ 5.10.247 (fixes >=2.6.35)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (47 versions)
  • every version up to 5.10.247-1: fixed in 5.10.247-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.158-1~deb11u1 (13 versions)
  • every version up to 6.1.159-1~deb11u1: fixed in 6.1.159-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (45 versions)
  • every version up to 6.1.159-1: fixed in 6.1.159-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.63-1~bpo12+1 (8 versions)
  • every version up to 6.12.63-1: fixed in 6.12.63-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.17.9-1 (82 versions)
  • every version up to 6.17.11-1: fixed in 6.17.11-1
—

Additional Vendor Advisories

(10)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 29× in last 7d / 94× 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 291 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 192 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2025-68285?
CVE-2025-68285 is a critical-severity vulnerability; its CVE record was published on December 16, 2025. In the Linux kernel, the following vulnerability has been resolved: libceph: fix potential use-after-free in havemonandosdmap() The wait loop in cephopensession() can race with the client receiving a new monmap or osdmap shortly after the initial map is received. Both cephmonchandlemap() and…
When was the CVE record for CVE-2025-68285 published?
The CVE record for CVE-2025-68285 was published on December 16, 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 14, 2026; the record at its source may have been updated since.
Is CVE-2025-68285 actively exploited?
CVE-2025-68285 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-68285?
CVE-2025-68285 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-68285?
A fix for CVE-2025-68285 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-68285 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-68285?

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

Book a Demo →Browse All CVEs