CVE-2026-45282

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (22nd 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-2026-33707 (ENISA EUVD)Source: ENISA EUVD

6.5EG
EchelonGraph verdictMonitorNo release containing the referenced fix is confirmed: check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

Nextcloud is an open source content collaboration platform. In Nextcloud Server from versions 32.0.0 to before 32.0.9, and 33.0.0 to before 33.0.3, an authenticated attacker can access attachments of link shares when knowing the share token, circumventing password protection or download restrictions. It is applicable to any file that is shared directly, as the attacker only needs to know a documentId they own, apart of the mentioned share token. For shared folders the attacker has to know or guess a documentId of a file that is included inside the folder, making it much harder to exploit. The attacker can only extract an attachments, but not the file shared file or folder itself. It is recommended that the Nextcloud Server is upgraded to 33.0.3 or 32.0.9. It is recommended that the Nextcloud Enterprise Server is upgraded to 33.0.3, 32.0.9, 31.0.14.5, 30.0.17.9, 29.0.16.16, 28.0.14.17 or 27.1.11.5

CVSS v3
6.5
EG Score
6.5MEDIUMmedium 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)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 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 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 referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.
EPSS PROB
0.3%
EPSS %ILE
22nd
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.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 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.3% within 30 daysSource: FIRST EPSS. 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.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.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 every mission impact level.

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.

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.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

The score's inputs: 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

June 1, 2026

Last Modified

July 22, 2026

Advisory Details (2)

Auto-updated Jun 13, 2026
Fix referenced — no release confirmed yet. Sources: github, github_pr.
GitHub pull request

fix: always validate share token if provided

Fix merged in nextcloud/text PR #8499 on 2026-04-22 — awaiting tagged release

https://github.com/nextcloud/text/pull/8499
GitHub advisoryMentions a patch (unverified)

Logged-in user bypasses share password and download restrictions on Text attachments via documentId · Advisory · nextcloud/security-advisories · GitHub

https://github.com/nextcloud/security-advisories/security/advisories/GHSA-35fx-69q6-xpjr

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 31× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 193 rows 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. None are among the latest 100 rows. The 93 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-45282?
CVE-2026-45282 is a medium-severity vulnerability; its CVE record was published on June 1, 2026. Nextcloud is an open source content collaboration platform. In Nextcloud Server from versions 32.0.0 to before 32.0.9, and 33.0.0 to before 33.0.3, an authenticated attacker can access attachments of link shares when knowing the share token, circumventing password protection or download…
When was the CVE record for CVE-2026-45282 published?
The CVE record for CVE-2026-45282 was published on June 1, 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 July 22, 2026; the record at its source may have been updated since.
Is CVE-2026-45282 actively exploited?
CVE-2026-45282 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-45282?
CVE-2026-45282 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-45282?
A fix for CVE-2026-45282 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-45282

Explore →

Is Your Infrastructure Affected by CVE-2026-45282?

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