CVE-2026-45414: Decidim: JWT-backed authentication can be replayed across organizations
Description A JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL participantDetails field for an Org 2 participant. The same trust-boundary problem also affects API-user authentication: an Org 1 API user can use a JWT on the Org 1 host and replay that JWT to the Org 2 API to read Org 2 participant personal data and reach Org 2's proposal.answer mutation path.
Published Jul 13, 2026
Affected packages
decidim
- Ecosystem
- RubyGems
- Affected
- < 0.31.5
- Fixed in
- 0.31.5
- Check
bundle info decidim
decidim
- Ecosystem
- RubyGems
- Affected
- >= 0.32.0.rc1, < 0.32.0
- Fixed in
- 0.32.0
- Check
bundle info decidim
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Description
A JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL participantDetails field for an Org 2 participant. The same trust-boundary problem also affects API-user authentication: an Org 1 API user can use a JWT on the Org 1 host and replay that JWT to the Org 2 API to read Org 2 participant personal data and reach Org 2's proposal.answer mutation path.
Technical description
The current host selects the Decidim organization context, but JWT-backed API authentication is not sufficiently bound to that host organization. As a result, the API can process a request in Org 2's context while still trusting an authenticated principal from Org 1.
Reproduction steps:
- Use an API key provided by the system administrator that is assigned to organization 1 to create the JWT token or
get the JWT token shown in the response when logged in as the organization admin.
- When using this JWT token it is possible to retrieve details from other organisations. Notice the change of the host header in the request below to that of another tenant
org2.localhost:3001
Note that using a participant-generated JWT did not allow showing these results.
Impact
A JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization.
Patches
See https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756
Workarounds
Disable JWT credentials on system panel (/system)
References
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.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More RubyGems vulnerabilities
All RubyGems entriesCVE-2025-65017
Decidim's private data exports can lead to data leaks
high8.2Feb 3, 2026CVE-2024-41673
Decidim has a cross-site scripting vulnerability in the version control page
high7.1Oct 1, 2024CVE-2024-39910
Decidim::Admin vulnerable to cross-site scripting (XSS) in the admin panel with QuillJS WYSWYG editor
medium5.4Sep 16, 2024CVE-2024-27090
Decidim vulnerable to data disclosure through the embed feature
medium5.3Jul 10, 2024CVE-2024-32469
Decidim cross-site scripting (XSS) in the pagination
medium7.1Jul 10, 2024CVE-2023-47634
Race condition in Endorsements
low3.1Feb 20, 2024
