CVE-2026-32109

MEDIUMNVD 4.44.4
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 4.4 under NVD CVSS v3. EPSS exploit probability: 0.2% (8th 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 week
4.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.2%CVSS: 4.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Copyparty is a portable file server. Prior to 1.20.12, if an attacker has been given both read- and write-permissions to the server, they can upload a malicious file with the filename .prologue.html and then craft a link to potentially execute arbitrary JavaScript in the victim's context. Note that it is intended behavior that the JavaScript would execute if the target clicks a link to the HTML file itself; "https://example.com/foo/.prologue.html". The vulnerability is that "https://example.com/foo/?b" would also evaluate the file, making the behavior unexpected. There are existing preventative measures (strict SameSite cookies) which makes it harder to leverage this vulnerability in an attack; in order to gain control of the target's authenticated session, the link must be clicked from a page served by the server itself -- most likely by editing an existing resource, which would require additional access permissions. Finally, for this attack to be successful, the attacker's target must click the specific crafted link given by the attacker. This vulnerability is not activated by normally browsing the web-UI on the server. This vulnerability is fixed in 1.20.12.

CVSS v3
4.4
EG Score
4.4MEDIUMmedium confidence
EG Risk
20
EG Risk 20/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity44% × 45%
The EG Score, 4.4 of 10.
Exploitation0.2% × 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.2%
EPSS %ILE
8th
KEV
Not listed

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

March 12, 2026

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Aug 7, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

Unexpected JavaScript execution via crafted URL to folder with `.prologue.html` · Advisory · 9001/copyparty · GitHub

https://github.com/9001/copyparty/security/advisories/GHSA-rcp6-88mm-9vgf

Vendor Advisories for CVE-2026-32109(1)

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

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
copyparty0.10.0 ... 1.9.9 (368 versions)
  • every version up to 1.20.12: fixed in 1.20.12
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 27× 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 89 of 159 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. 11 repeat rows among the latest 100 are merged into the row they repeat. The 70 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-32109?
CVE-2026-32109 is a medium-severity vulnerability; its CVE record was published on March 12, 2026. Copyparty is a portable file server. Prior to 1.20.12, if an attacker has been given both read- and write-permissions to the server, they can upload a malicious file with the filename .prologue.html and then craft a link to potentially execute arbitrary JavaScript in the victim's context. Note that…
When was the CVE record for CVE-2026-32109 published?
The CVE record for CVE-2026-32109 was published on March 12, 2026. 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 June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-32109 actively exploited?
CVE-2026-32109 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-32109?
CVE-2026-32109 has a CVSS v3 base score of 4.4 (NVD).
How do I remediate CVE-2026-32109?
A fix for CVE-2026-32109 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-32109 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-2026-32109

Explore →

Is Your Infrastructure Affected by CVE-2026-32109?

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

Book a Demo →Browse All CVEs