CVE-2025-39779

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory published 2025-09-11. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2025-28934 (ENISA EUVD) · GHSA-84m7-9982-88x5 (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
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.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

btrfs: subpage: keep TOWRITE tag until folio is cleaned

btrfs_subpage_set_writeback() calls folio_start_writeback() the first time a folio is written back, and it also clears the PAGECACHE_TAG_TOWRITE tag even if there are still dirty blocks in the folio. This can break ordering guarantees, such as those required by btrfs_wait_ordered_extents().

That ordering breakage leads to a real failure. For example, running generic/464 on a zoned setup will hit the following ASSERT. This happens because the broken ordering fails to flush existing dirty pages before the file size is truncated.

assertion failed: !list_empty(&ordered->list) :: 0, in fs/btrfs/zoned.c:1899 ------------[ cut here ]------------ kernel BUG at fs/btrfs/zoned.c:1899! Oops: invalid opcode: 0000 [#1] SMP NOPTI CPU: 2 UID: 0 PID: 1906169 Comm: kworker/u130:2 Kdump: loaded Not tainted 6.16.0-rc6-BTRFS-ZNS+ #554 PREEMPT(voluntary) Hardware name: Supermicro Super Server/H12SSL-NT, BIOS 2.0 02/22/2021 Workqueue: btrfs-endio-write btrfs_work_helper [btrfs] RIP: 0010:btrfs_finish_ordered_zoned.cold+0x50/0x52 [btrfs] RSP: 0018:ffffc9002efdbd60 EFLAGS: 00010246 RAX: 000000000000004c RBX: ffff88811923c4e0 RCX: 0000000000000000 RDX: 0000000000000000 RSI: ffffffff827e38b1 RDI: 00000000ffffffff RBP: ffff88810005d000 R08: 00000000ffffdfff R09: ffffffff831051c8 R10: ffffffff83055220 R11: 0000000000000000 R12: ffff8881c2458c00 R13: ffff88811923c540 R14: ffff88811923c5e8 R15: ffff8881c1bd9680 FS: 0000000000000000(0000) GS:ffff88a04acd0000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f907c7a918c CR3: 0000000004024000 CR4: 0000000000350ef0 Call Trace: ? srso_return_thunk+0x5/0x5f btrfs_finish_ordered_io+0x4a/0x60 [btrfs] btrfs_work_helper+0xf9/0x490 [btrfs] process_one_work+0x204/0x590 ? srso_return_thunk+0x5/0x5f worker_thread+0x1d6/0x3d0 ? __pfx_worker_thread+0x10/0x10 kthread+0x118/0x230 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x205/0x260 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30

Consider process A calling writepages() with WB_SYNC_NONE. In zoned mode or for compressed writes, it locks several folios for delalloc and starts writing them out. Let's call the last locked folio folio X. Suppose the write range only partially covers folio X, leaving some pages dirty. Process A calls btrfs_subpage_set_writeback() when building a bio. This function call clears the TOWRITE tag of folio X, whose size = 8K and the block size = 4K. It is following state.

0 4K 8K |/////|/////| (flag: DIRTY, tag: DIRTY) <-----> Process A will write this range.

Now suppose process B concurrently calls writepages() with WB_SYNC_ALL. It calls tag_pages_for_writeback() to tag dirty folios with PAGECACHE_TAG_TOWRITE. Since folio X is still dirty, it gets tagged. Then, B collects tagged folios using filemap_get_folios_tag() and must wait for folio X to be written before returning from writepages().

0 4K 8K |/////|/////| (flag: DIRTY, tag: DIRTY|TOWRITE)

However, between tagging and collecting, process A may call btrfs_subpage_set_writeback() and clear folio X's TOWRITE tag. 0 4K 8K | |/////| (flag: DIRTY|WRITEBACK, tag: DIRTY)

As a result, process B won't see folio X in its batch, and returns without waiting for it. This breaks the WB_SYNC_ALL ordering requirement.

Fix this by using btrfs_subpage_set_writeback_keepwrite(), which retains the TOWRITE tag. We now manually clear the tag only after the folio becomes clean, via the xas operation.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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.2%
EPSS %ILE
4th
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% 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, 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).

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

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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 11, 2025

Last Modified

October 19, 2026

Advisory Details (3)

Auto-updated Aug 2, 2026
Patch available.
Web page

btrfs: subpage: keep TOWRITE tag until folio is cleaned - kernel/git/stable/linux.git - Linux kernel stable tree

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

btrfs: subpage: keep TOWRITE tag until folio is cleaned - kernel/git/stable/linux.git - Linux kernel stable tree

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

btrfs: subpage: keep TOWRITE tag until folio is cleaned - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3d61136945a7008fc90d013c3c67007ce0c96131

Vendor Advisories for CVE-2025-39779(1)

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

Patch Availability(17)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1047.50+fips1) @ noble2026-10-19ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-100.100.1) @ noble2026-10-19ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1046.49.1) @ noble2026-10-19ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1044.44) @ noble2026-10-19ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1023.24) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1046.52+fips1) @ noble2026-10-19ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1041.42) @ noble2026-10-19ubuntu
ubuntulinux-virtual-6.8 (6.8.0-100.100) @ noble2026-10-19ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1047.50~22.04.2) @ jammy2026-10-19ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1041.42~22.04.1) @ jammy2026-10-19ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-100.100+fips1) @ noble2026-10-19ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1043.44) @ noble2026-10-19ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-100.100~22.04.1) @ jammy2026-10-19ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-10-19ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1046.52) @ noble2026-10-19ubuntu
ubuntulinux-tools-gke-64k-6.8 (6.8.0-1043.48) @ noble2026-10-19ubuntu
linuxKernel @ 6.12.44 (fixes >=5.13.0)—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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1, 6.12.41-1, 6.12.43-1, 6.12.43-1~bpo12+1
  • every version up to 6.12.48-1: fixed in 6.12.48-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.16~rc7-1~exp1 (63 versions)
  • every version up to 6.16.5-1: fixed in 6.16.5-1
—

Additional Vendor Advisories

(16)

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 7× in last 7d / 40× 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 196 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 98 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2025-39779?
CVE-2025-39779 is a medium-severity vulnerability; its CVE record was published on September 11, 2025. In the Linux kernel, the following vulnerability has been resolved: btrfs: subpage: keep TOWRITE tag until folio is cleaned btrfs_subpage_set_writeback() calls folio_start_writeback() the first time a folio is written back, and it also clears the PAGECACHE_TAG_TOWRITE tag even if there are still…
When was the CVE record for CVE-2025-39779 published?
The CVE record for CVE-2025-39779 was published on September 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 19, 2026; the record at its source may have been updated since.
Is CVE-2025-39779 actively exploited?
CVE-2025-39779 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-39779?
CVE-2025-39779 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-39779?
A fix for CVE-2025-39779 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-39779 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-39779

Explore →

Is Your Infrastructure Affected by CVE-2025-39779?

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

Book a Demo →Browse All CVEs