GHSA-767h-63j4-5226 is a medium-severity (CVSS 6.5) Information Exposure vulnerability in decidim-core. O3 Security confirms whether GHSA-767h-63j4-5226 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Decidim: Private exports can be downloaded through reusable links
Real-World Exposure
decidim-core💎decidim-core💎decidim-coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.
Description
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.
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.
Patches
See https://github.com/decidim/decidim/pull/16680
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 💎RubyGems | decidim-core | all versions | 0.30.9 |
| 💎RubyGems | decidim-core | ≥ 0.31.0.rc1&&< 0.31.5 | 0.31.5 |
| 💎RubyGems | decidim-core | ≥ 0.32.0.rc1&&< 0.32.0 | 0.32.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for decidim-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update decidim-core to 0.30.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-767h-63j4-5226 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-767h-63j4-5226 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-767h-63j4-5226. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-767h-63j4-5226 in your dependencies?
O3 detects GHSA-767h-63j4-5226 across RubyGems dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.