## Description Scanned identity-document images provided by participants and shown in the verification admin workflow are exposed through signed `/rails/active_storage/disk/` URLs that can be fetched without any authenticated session. Anyone who obtains one of those URLs can retrieve the document until the signature expires. ## Technical description This issue comes from the verification admin UI exposing scanned documents through reusable Active Storage disk links. Verification-document images are rendered with `variant_url(...)`, which produces signed `/rails/active_storage/disk/...` links instead of routing the file through an authorization-checking controller. Because Decidim configures Active Storage service URLs to remain valid for seven days, the URL itself becomes the credential for that period. The affected files are `verification_attachment` blobs on Decidim::Authorization, and the admin review pages embed those signed URLs directly into the HTML for pending and confirmation views. Reproduction steps: 1. Create a fresh verification document as a normal user. 1.1. Open http://localhost:3001/users/sign_in. 1.2. Open http://localhost:3001/id_documents/authorizations/new. 1.3. Submit an id_documents verification request with an image attachment. 2. Open the admin review page that renders the attachment. 2.1. Sign out. 2.2. Sign back in as [email protected]. 2.3. Try http://localhost:3001/admin/id_documents. 3. Harvest the signed Active Storage URL. 3.1. Open DevTools Network before loading the review page. 3.2. Reload the page. 3.3. Copy one request URL matching `http://localhost:3001/rails/active_storage/disk/<SIGNED_TOKEN>/<FILENAME>`. 4. Replay the file URL without any Decidim session. 4.1. Open a private window or a second browser where you are not signed in to Decidim. 4.2. Paste the exact copied /rails/active_storage/disk/... URL. 4.3. Confirm the verification image still loads. ### Impact - This only applies to Organizations using the "Identity documents" verification - Any party that obtains one of these URLs can download the underlying scanned identity document for the lifetime of the signed link without needing to authenticate as the reviewing admin. - In the reproduced case, that replay window was about seven days, which is long enough for routine leakage channels such as copied links, screenshots, logs, browser history, and support workflows to become realistic exfiltration paths. - This raises the risk of leakage through browser history, screenshots, copy-paste, support tickets, logs, analytics tooling, malicious browser extensions, or any other channel that captures full URLs. - Because the affected files are identity-verification documents, the exposed data can include highly sensitive personal information. ### Patches See https://github.com/decidim/decidim/pull/16680 ### Workarounds Disable the "Identity documents" verification ### Reference OWASP A01:2021 Broken Access Control ### Credits This issue was discovered in a security audit organized by the [Decidim Association](https://decidim.org) and made by [Radically Open Security](https://www.radicallyopensecurity.com/) against Decidim financed by [NGI](https://ngi.eu/).
## Description Scanned identity-document images provided by participants and shown in the verification admin workflow are exposed through signed `/rails/active_storage/disk/` URLs that can be fetched without any authenticated session. Anyone who obtains one of those URLs can retrieve the document until the signature expires. ## Technical description This issue comes from the verification admin UI exposing scanned documents through reusable Active Storage disk links. Verification-document images are rendered with `variant_url(...)`, which produces signed `/rails/active_storage/disk/...` links instead of routing the file through an authorization-checking controller. Because Decidim configures Active Storage service URLs to remain valid for seven days, the URL itself becomes the credential for that period. The affected files are `verification_attachment` blobs on Decidim::Authorization, and the admin review pages embed those signed URLs directly into the HTML for pending and confirmation views. Reproduction steps: 1. Create a fresh verification document as a normal user. 1.1. Open http://localhost:3001/users/sign_in. 1.2. Open http://localhost:3001/id_documents/authorizations/new. 1.3. Submit an id_documents verification request with an image attachment. 2. Open the admin review page that renders the attachment. 2.1. Sign out. 2.2. Sign back in as [email protected]. 2.3. Try http://localhost:3001/admin/id_documents. 3. Harvest the signed Active Storage URL. 3.1. Open DevTools Network before loading the review page. 3.2. Reload the page. 3.3. Copy one request URL matching `http://localhost:3001/rails/active_storage/disk/<SIGNED_TOKEN>/<FILENAME>`. 4. Replay the file URL without any Decidim session. 4.1. Open a private window or a second browser where you are not signed in to Decidim. 4.2. Paste the exact copied /rails/active_storage/disk/... URL. 4.3. Confirm the verification image still loads. ### Impact - This only applies to Organizations using the "Identity documents" verification - Any party that obtains one of these URLs can download the underlying scanned identity document for the lifetime of the signed link without needing to authenticate as the reviewing admin. - In the reproduced case, that replay window was about seven days, which is long enough for routine leakage channels such as copied links, screenshots, logs, browser history, and support workflows to become realistic exfiltration paths. - This raises the risk of leakage through browser history, screenshots, copy-paste, support tickets, logs, analytics tooling, malicious browser extensions, or any other channel that captures full URLs. - Because the affected files are identity-verification documents, the exposed data can include highly sensitive personal information. ### Patches See https://github.com/decidim/decidim/pull/16680 ### Workarounds Disable the "Identity documents" verification ### Reference OWASP A01:2021 Broken Access Control ### Credits This issue was discovered in a security audit organized by the [Decidim Association](https://decidim.org) and made by [Radically Open Security](https://www.radicallyopensecurity.com/) against Decidim financed by [NGI](https://ngi.eu/).
Update decidim-verifications to 0.30.9; decidim-verifications to 0.31.5; decidim-verifications to 0.32.0 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanDecidim: Verification documents can be downloaded through reusable links affects decidim-verifications (rubygems), decidim-verifications (rubygems), decidim-verifications (rubygems). Severity is high. ## Description Scanned identity-document images provided by participants and shown in the verification admin workflow are exposed through signed `/rails/active_storage/disk/` URLs that can be fetched without any authenticated session. Anyone who obtains one of those URLs can retrieve the document until the signature expires. ## Technical description This issue comes from the verification admin UI exposing scanned documents through reusable Active Storage disk links. Verification-document images are rendered with `variant_url(...)`, which produces signed `/rails/active_storage/disk/...` links instead of routing the file through an authorization-checking controller. Because Decidim configures Active Storage service URLs to remain valid for seven days, the URL itself becomes the credential for that period. The affected files are `verification_attachment` blobs on Decidim::Authorization, and the admin review pages embed those signed URLs directly into the HTML for pending and confirmation views. Reproduction steps: 1. Create a fresh verification document as a normal user. 1.1. Open http://localhost:3001/users/sign_in. 1.2. Open http://localhost:3001/id_documents/authorizations/new. 1.3. Submit an id_documents verification request with an image attachment. 2. Open the admin review page that renders the attachment. 2.1. Sign out. 2.2. Sign back in as [email protected]. 2.3. Try http://localhost:3001/admin/id_documents. 3. Harvest the signed Active Storage URL. 3.1. Open DevTools Network before loading the review page. 3.2. Reload the page. 3.3. Copy one request URL matching `http://localhost:3001/rails/active_storage/disk/<SIGNED_TOKEN>/<FILENAME>`. 4. Replay the file URL without any Decidim session. 4.1. Open a private window or a second browser where you are not signed in to Decidim. 4.2. Paste the exact copied /rails/active_storage/disk/... URL. 4.3. Confirm the verification image still loads. ### Impact - This only applies to Organizations using the "Identity documents" verification - Any party that obtains one of these URLs can download the underlying scanned identity document for the lifetime of the signed link without needing to authenticate as the reviewing admin. - In the reproduced case, that replay window was about seven days, which is long enough for routine leakage channels such as copied links, screenshots, logs, browser history, and support workflows to become realistic exfiltration paths. - This raises the risk of leakage through browser history, screenshots, copy-paste, support tickets, logs, analytics tooling, malicious browser extensions, or any other channel that captures full URLs. - Because the affected files are identity-verification documents, the exposed data can include highly sensitive personal information. ### Patches See https://github.com/decidim/decidim/pull/16680 ### Workarounds Disable the "Identity documents" verification ### Reference OWASP A01:2021 Broken Access Control ### Credits This issue was discovered in a security audit organized by the [Decidim Association](https://decidim.org) and made by [Radically Open Security](https://www.radicallyopensecurity.com/) against Decidim financed by [NGI](https://ngi.eu/).
AI coding agents often install or upgrade packages automatically in rubygems. A high vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| decidim-verificationsrubygems | <0.30.9 | 0.30.9 |
| decidim-verificationsrubygems | >=0.31.0.rc1,<0.31.5 | 0.31.5 |
| decidim-verificationsrubygems | >=0.32.0.rc1,<0.32.0 | 0.32.0 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL GuardUpdate decidim-verifications to 0.30.9; decidim-verifications to 0.31.5; decidim-verifications to 0.32.0 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanDecidim: Verification documents can be downloaded through reusable links affects decidim-verifications (rubygems), decidim-verifications (rubygems), decidim-verifications (rubygems). Severity is high. ## Description Scanned identity-document images provided by participants and shown in the verification admin workflow are exposed through signed `/rails/active_storage/disk/` URLs that can be fetched without any authenticated session. Anyone who obtains one of those URLs can retrieve the document until the signature expires. ## Technical description This issue comes from the verification admin UI exposing scanned documents through reusable Active Storage disk links. Verification-document images are rendered with `variant_url(...)`, which produces signed `/rails/active_storage/disk/...` links instead of routing the file through an authorization-checking controller. Because Decidim configures Active Storage service URLs to remain valid for seven days, the URL itself becomes the credential for that period. The affected files are `verification_attachment` blobs on Decidim::Authorization, and the admin review pages embed those signed URLs directly into the HTML for pending and confirmation views. Reproduction steps: 1. Create a fresh verification document as a normal user. 1.1. Open http://localhost:3001/users/sign_in. 1.2. Open http://localhost:3001/id_documents/authorizations/new. 1.3. Submit an id_documents verification request with an image attachment. 2. Open the admin review page that renders the attachment. 2.1. Sign out. 2.2. Sign back in as [email protected]. 2.3. Try http://localhost:3001/admin/id_documents. 3. Harvest the signed Active Storage URL. 3.1. Open DevTools Network before loading the review page. 3.2. Reload the page. 3.3. Copy one request URL matching `http://localhost:3001/rails/active_storage/disk/<SIGNED_TOKEN>/<FILENAME>`. 4. Replay the file URL without any Decidim session. 4.1. Open a private window or a second browser where you are not signed in to Decidim. 4.2. Paste the exact copied /rails/active_storage/disk/... URL. 4.3. Confirm the verification image still loads. ### Impact - This only applies to Organizations using the "Identity documents" verification - Any party that obtains one of these URLs can download the underlying scanned identity document for the lifetime of the signed link without needing to authenticate as the reviewing admin. - In the reproduced case, that replay window was about seven days, which is long enough for routine leakage channels such as copied links, screenshots, logs, browser history, and support workflows to become realistic exfiltration paths. - This raises the risk of leakage through browser history, screenshots, copy-paste, support tickets, logs, analytics tooling, malicious browser extensions, or any other channel that captures full URLs. - Because the affected files are identity-verification documents, the exposed data can include highly sensitive personal information. ### Patches See https://github.com/decidim/decidim/pull/16680 ### Workarounds Disable the "Identity documents" verification ### Reference OWASP A01:2021 Broken Access Control ### Credits This issue was discovered in a security audit organized by the [Decidim Association](https://decidim.org) and made by [Radically Open Security](https://www.radicallyopensecurity.com/) against Decidim financed by [NGI](https://ngi.eu/).
AI coding agents often install or upgrade packages automatically in rubygems. A high vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| decidim-verificationsrubygems | <0.30.9 | 0.30.9 |
| decidim-verificationsrubygems | >=0.31.0.rc1,<0.31.5 | 0.31.5 |
| decidim-verificationsrubygems | >=0.32.0.rc1,<0.32.0 | 0.32.0 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard