# CVE-2026-45377: Decidim: Private exports can be downloaded through reusable links

> Attackers can access private user data exports by replaying signed Active Storage URLs without authentication, exposing sensitive information.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 31 Jul 2026
- **Updated:** 31 Jul 2026
- **Also known as:** GHSA-767h-63j4-5226

## What is CVE-2026-45377?

CVE-2026-45377 is a medium-severity vulnerability in decidim, published on 31 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Decidim is a participatory democracy framework. Prior to 0.30.9, from 0.31.0 before 0.31.5, and in 0.32.0.rc1 before 0.32.0.rc2, the normal download_your_data flow requires the requester to be logged in as the export owner, but the resulting Active Storage blob redirect URL can be replayed without authentication by anyone who obtains it. This is because Decidim::DownloadYourDataController#download_file authenticates the export owner but redirects to a signed Active Storage blob URL that is no longer bound to the owner session. This issue is fixed in versions 0.30.9, 0.31.5, and 0.32.0.rc2.

Weakness: CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-45377?

6 open source packages ship an affected version, including decidim-core.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `decidim-core` | RubyGems | All versions | 0.30.9 |
| `decidim-core` | RubyGems | All versions | 0.30.9 |
| `decidim-core` | RubyGems | From 0.31.0.rc1 | 0.31.5 |
| `decidim-core` | RubyGems | From 0.31.0.rc1 | 0.31.5 |
| `decidim-core` | RubyGems | From 0.32.0.rc1 | 0.32.0 |
| `decidim-core` | RubyGems | From 0.32.0.rc1 | 0.32.0 |

## How do I fix CVE-2026-45377?

Upgrade decidim-core to a fixed version for your release line: 0.30.9, 0.31.5 or 0.32.0.

## Is CVE-2026-45377 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45377 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-45377 and fix it if it is affected.

What it is: CVE-2026-45377 is a medium-severity vulnerability in decidim, published on 31 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45377 exists.

Affected packages and fixed versions:
- decidim-core (RubyGems): affected all versions; fixed in 0.30.9
- decidim-core (RubyGems): affected all versions; fixed in 0.30.9
- decidim-core (RubyGems): affected from 0.31.0.rc1; fixed in 0.31.5
- decidim-core (RubyGems): affected from 0.31.0.rc1; fixed in 0.31.5
- decidim-core (RubyGems): affected from 0.32.0.rc1; fixed in 0.32.0
- decidim-core (RubyGems): affected from 0.32.0.rc1; fixed in 0.32.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-45377/ (Markdown: https://insights.sbomify.com/CVE-2026-45377/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-45377
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-45377
- OSV: https://osv.dev/vulnerability/CVE-2026-45377

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-45377/
Summaries are generated and may contain mistakes; the official description above is the record.