Summary
Decidim: Private exports can be downloaded through reusable links
Description
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.
Technical description
This private export flow turns an authenticated, user-scoped download into a reusable bearer link because the protected Decidim endpoint redirects to the underlying Active Storage blob URL. Decidim::DownloadYourDataController#download_file correctly scopes the export record to current_user, so the wrapper route itself is not directly accessible to another user. However, once the owner
performs that authenticated GET request, the response redirects to a signed Active Storage URL that is no longer bound to the user session. Anyone who learns that URL can replay it and retrieve the file without being logged in as the export owner.
Because the blob redirect URL is delivered through a GET request and appears in the redirect chain, it is more likely to leak through browser history, logs, proxy tooling, screenshots, copied links, support transcripts, or other client-side handling of URLs.
Reproduction steps:
Step 1. Generate or locate a completed export in the Web UI.
- Sign in as
[email protected]athttp://localhost:3001/users/sign_in. - Open
http://localhost:3001/download_your_data. - Request a new export from the page and wait until the export becomes downloadable.
- Open the completed export entry from the list and copy its wrapper URL, for example
http://localhost:3001/download_your_data/download?uuid=07286e61-932d-46d4-bd74-bcd1340c503f.
Step 2. Download through the authenticated wrapper route.
- While still signed in as [email protected], open the wrapper URL in the browser.
- Confirm that this Decidim route requires the owner session and is not directly usable when logged out or when logged in as another user.
Step 3. Capture the final bearer URL in the redirect chain.
- In DevTools Network or Burp, inspect the redirect sequence for the wrapper request.
- Copy the Active Storage redirect URL, typically matching
http://localhost:3001/rails/active_storage/blobs/redirect/<SIGNED_ID>/<FILENAME>. - Note that the Active Storage redirect URL is no longer protected by the Decidim ownership check.
Step 4. Replay the final file URL without authentication.
- Open a private window or separate browser with no Decidim session.
- Paste the copied
http://localhost:3001/rails/active_storage/blobs/redirect/<SIGNED_ID>/<FILENAME>URL. - Confirm the export file still downloads even though you are not logged in as the export owner.
Workarounds
Disable Private Downloads URLs
Reference
OWASP A01:2021 Broken Access Control
Credits
This issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI.
Impact
Personal data exports can be retrieved through leakage channels such as browser history, logs, referrers, screenshots, copied links, support transcripts, intercepted email content, or other client-side disclosure of the GET URL.
CVE-2026-45377 has a CVSS score of 6.5 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.30.9, 0.31.5, 0.32.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Frequently Asked Questions
- What is CVE-2026-45377? CVE-2026-45377 is a medium-severity security vulnerability in decidim-core (rubygems), affecting versions < 0.30.9. It is fixed in 0.30.9, 0.31.5, 0.32.0.
- How severe is CVE-2026-45377? CVE-2026-45377 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of decidim-core are affected by CVE-2026-45377? decidim-core (rubygems) versions < 0.30.9 is affected.
- Is there a fix for CVE-2026-45377? Yes. CVE-2026-45377 is fixed in 0.30.9, 0.31.5, 0.32.0. Upgrade to this version or later.
- Is CVE-2026-45377 exploitable, and should I be worried? Whether CVE-2026-45377 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-45377 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-45377?
- Upgrade
decidim-coreto 0.30.9 or later - Upgrade
decidim-coreto 0.31.5 or later - Upgrade
decidim-coreto 0.32.0 or later
- Upgrade