decidim
The participatory democracy framework. A generator and multiple gems made with Ruby on Rails
Activity
- Latest release
- 1mo ago
- Total releases
- 178
- Cadence
- ~2 days
- Last 12 months
- 23
Reach
- Stars
- 1.8k
Details
- License
- unknown
- First release
- Sep 16, 2016
| Version | Released | |
|---|---|---|
0.32.1
patch
|
0.32.1
patch
Dependencies (21)
+ 13 more
Changelog
Compare changes
|
|
0.31.7
patch
|
0.31.7
patch
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.31.6
patch
|
0.31.6
patch
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.32.0
minor
|
0.32.0
minor
Dependencies (21)
+ 13 more
Changelog
Compare changes
|
|
0.32.0.rc3
pre
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.32.0.rc3
pre
Dependencies (21)
+ 13 more
Changelog
Compare changes
|
|
0.32.0.rc2
pre
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.32.0.rc2
pre
Dependencies (21)
+ 13 more
Changelog
Compare changes
|
|
0.31.5
patch
|
0.31.5
patch
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.30.9
patch
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.30.9
patch
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.32.0.rc1
pre
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.32.0.rc1
pre
Dependencies (21)
+ 13 more
Changelog
Compare changes
|
|
0.31.4
patch
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.31.4
patch
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.30.8
patch
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.30.8
patch
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.30.7
patch
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.30.7
patch
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.31.3
patch
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.31.3
patch
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.30.6
patch
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.30.6
patch
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.31.2
patch
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.31.2
patch
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.30.5
patch
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.30.5
patch
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.31.1
patch
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.31.1
patch
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.30.4
patch
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.30.4
patch
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.29.7
patch
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.29.7
patch
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.31.0
minor
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.31.0
minor
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.29.6
patch
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.29.6
patch
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.30.3
patch
2 CVEs
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev
CVE-2025-65017
GHSA-3cx6-j9j4-54mp
Feb 03, 2026
Decidim's private data exports can lead to data leaks
High
Network
Low
Low
ImpactPrivate data exports can lead to data leaks in cases where the UUID generation causes collisions for the generated UUIDs. The bug was introduced by #13571 and affects Decidim versions 0.30.0 or newer (currently 2025-09-23). This issue was discovered by running the following spec several times in a row, as it can randomly fail due to this bug:
Run the spec as many times as needed to hit a UUID that converts to The UUID to zero conversion does not cause a security issue but the security issue is demonstrated with the following example. The following code regenerates the issue by assigning a predefined UUID that will generate a collision (example assumes there are already two existing users in the system):
Expect to see an error in the situation. Now, login as user with ID 1, go to The reason for the test case failure can be replicated in case you change the export ID to After attaching that ID, you can test if the file is available for the export:
Note that this fails with such UUID as shown in the example and could easily lead to collisions in case the UUID starts with a number. E.g. UUID Theoretical chance of collision (the reality depends on the UUID generation algorithm):
The root cause is that the class WorkaroundsFully disable the private exports feature until a patch is available. Affected versions
0.30.0
0.30.1
0.30.2
0.30.3
Fixed in
0.30.4
References
Updated Feb 08, 2026 · Source: OSV.dev |
0.30.3
patch
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.31.0.rc2
pre
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.31.0.rc2
pre
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.31.0.rc1
pre
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.31.0.rc1
pre
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.30.2
patch
2 CVEs
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev
CVE-2025-65017
GHSA-3cx6-j9j4-54mp
Feb 03, 2026
Decidim's private data exports can lead to data leaks
High
Network
Low
Low
ImpactPrivate data exports can lead to data leaks in cases where the UUID generation causes collisions for the generated UUIDs. The bug was introduced by #13571 and affects Decidim versions 0.30.0 or newer (currently 2025-09-23). This issue was discovered by running the following spec several times in a row, as it can randomly fail due to this bug:
Run the spec as many times as needed to hit a UUID that converts to The UUID to zero conversion does not cause a security issue but the security issue is demonstrated with the following example. The following code regenerates the issue by assigning a predefined UUID that will generate a collision (example assumes there are already two existing users in the system):
Expect to see an error in the situation. Now, login as user with ID 1, go to The reason for the test case failure can be replicated in case you change the export ID to After attaching that ID, you can test if the file is available for the export:
Note that this fails with such UUID as shown in the example and could easily lead to collisions in case the UUID starts with a number. E.g. UUID Theoretical chance of collision (the reality depends on the UUID generation algorithm):
The root cause is that the class WorkaroundsFully disable the private exports feature until a patch is available. Affected versions
0.30.0
0.30.1
0.30.2
0.30.3
Fixed in
0.30.4
References
Updated Feb 08, 2026 · Source: OSV.dev |
0.30.2
patch
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.29.5
patch
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.29.5
patch
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.30.1
patch
2 CVEs
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev
CVE-2025-65017
GHSA-3cx6-j9j4-54mp
Feb 03, 2026
Decidim's private data exports can lead to data leaks
High
Network
Low
Low
ImpactPrivate data exports can lead to data leaks in cases where the UUID generation causes collisions for the generated UUIDs. The bug was introduced by #13571 and affects Decidim versions 0.30.0 or newer (currently 2025-09-23). This issue was discovered by running the following spec several times in a row, as it can randomly fail due to this bug:
Run the spec as many times as needed to hit a UUID that converts to The UUID to zero conversion does not cause a security issue but the security issue is demonstrated with the following example. The following code regenerates the issue by assigning a predefined UUID that will generate a collision (example assumes there are already two existing users in the system):
Expect to see an error in the situation. Now, login as user with ID 1, go to The reason for the test case failure can be replicated in case you change the export ID to After attaching that ID, you can test if the file is available for the export:
Note that this fails with such UUID as shown in the example and could easily lead to collisions in case the UUID starts with a number. E.g. UUID Theoretical chance of collision (the reality depends on the UUID generation algorithm):
The root cause is that the class WorkaroundsFully disable the private exports feature until a patch is available. Affected versions
0.30.0
0.30.1
0.30.2
0.30.3
Fixed in
0.30.4
References
Updated Feb 08, 2026 · Source: OSV.dev |
0.30.1
patch
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.29.4
patch
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.29.4
patch
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.29.3
patch
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.29.3
patch
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.28.6
patch
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.28.6
patch
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.30.0
minor
2 CVEs
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev
CVE-2025-65017
GHSA-3cx6-j9j4-54mp
Feb 03, 2026
Decidim's private data exports can lead to data leaks
High
Network
Low
Low
ImpactPrivate data exports can lead to data leaks in cases where the UUID generation causes collisions for the generated UUIDs. The bug was introduced by #13571 and affects Decidim versions 0.30.0 or newer (currently 2025-09-23). This issue was discovered by running the following spec several times in a row, as it can randomly fail due to this bug:
Run the spec as many times as needed to hit a UUID that converts to The UUID to zero conversion does not cause a security issue but the security issue is demonstrated with the following example. The following code regenerates the issue by assigning a predefined UUID that will generate a collision (example assumes there are already two existing users in the system):
Expect to see an error in the situation. Now, login as user with ID 1, go to The reason for the test case failure can be replicated in case you change the export ID to After attaching that ID, you can test if the file is available for the export:
Note that this fails with such UUID as shown in the example and could easily lead to collisions in case the UUID starts with a number. E.g. UUID Theoretical chance of collision (the reality depends on the UUID generation algorithm):
The root cause is that the class WorkaroundsFully disable the private exports feature until a patch is available. Affected versions
0.30.0
0.30.1
0.30.2
0.30.3
Fixed in
0.30.4
References
Updated Feb 08, 2026 · Source: OSV.dev |
0.30.0
minor
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.27.10
patch
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.27.10
patch
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.30.0.rc3
pre
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.30.0.rc3
pre
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.30.0.rc2
pre
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.30.0.rc2
pre
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.30.0.rc1
pre
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.30.0.rc1
pre
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.29.2
patch
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.29.2
patch
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.28.5
patch
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.28.5
patch
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.28.4
patch
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.28.4
patch
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.29.1
patch
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.29.1
patch
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.28.3
patch
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.28.3
patch
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.29.0
minor
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.29.0
minor
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.27.9
patch
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.27.9
patch
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.29.0.rc4
pre
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.29.0.rc4
pre
Dependencies (23)
+ 15 more
Changelog
Compare changes
|
|
0.27.8
patch
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.27.8
patch
Dependencies (23)
+ 15 more
Changelog
Compare changes
|
|
0.29.0.rc3
pre
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.29.0.rc3
pre
Dependencies (23)
+ 15 more
Changelog
Compare changes
|
|
0.29.0.rc1
pre
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.29.0.rc1
pre
Dependencies (23)
+ 15 more
Changelog
Compare changes
|
|
0.28.2
patch
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.28.2
patch
Dependencies (23)
+ 15 more
Changelog
Compare changes
|
|
0.29.0.rc2
pre
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.29.0.rc2
pre
Dependencies (23)
+ 15 more
Changelog
Compare changes
|
|
0.27.7
patch
2 CVEs
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev
CVE-2024-41673
GHSA-cc4g-m3g7-xmw8
Oct 01, 2024
Decidim has a cross-site scripting vulnerability in the version control page
High
Network
Low
None
ImpactThe version control feature used in resources is subject to potential cross-site scripting (XSS) attack through a malformed URL. WorkaroundsNot available ReferencesOWASP ASVS v4.0.3-5.1.3 CreditsThis issue was discovered in a security audit organized by Open Source Politics against Decidim done during July 2025. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 114 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.3.0
0.3.1
0.3.2
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
Fixed in
0.27.8
References
Updated Oct 03, 2024 · Source: OSV.dev |
0.27.7
patch
Dependencies (23)
+ 15 more
Changelog
Compare changes
|
|
0.28.1
patch
1 CVE
CVE-2026-45414
GHSA-r3v7-5x4c-c69q
Jul 13, 2026
Decidim: JWT-backed authentication can be replayed across organizations
8.5
/ 10
High
Network
Low
Low
None
Changed
High
Low
None
DescriptionA JWT issued to an Org 1 account is accepted on the Org 2 API and can read the admin-only GraphQL Technical descriptionThe 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:
Note that using a participant-generated JWT did not allow showing these results. ImpactA JWT issued for one organization can be replayed successfully against another organization's API and used to retrieve sensitive details from that organization. PatchesSee https://github.com/decidim/decidim/pull/16673 and https://github.com/decidim/decidim/pull/16756 WorkaroundsDisable JWT credentials on system panel ( ReferencesOWASP A01:2021 Broken Access Control CreditsThis issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI. Affected versions
0.0.1
0.0.1.alpha1
0.0.1.alpha2
0.0.1.alpha3
0.0.1.alpha4
0.0.1.alpha5
0.0.1.alpha6
0.0.1.alpha7
0.0.1.alpha8
0.0.1.alpha9
0.0.2
0.0.3
+ 161 more Show less
0.0.4
0.0.5
0.0.6
0.0.7
0.0.8.1
0.1.0
0.10.0
0.10.1
0.11.0.pre1
0.11.1
0.11.2
0.12.0
0.12.0.pre
0.12.1
0.12.2
0.13.0
0.13.0.pre1
0.13.1
0.14.1
0.14.2
0.14.3
0.14.4
0.15.0
0.15.1
0.15.2
0.16.0
0.16.1
0.17.0
0.17.1
0.17.2
0.18.0
0.18.1
0.19.0
0.19.1
0.2.0
0.20.0
0.20.1
0.21.0
0.22.0
0.23.0
0.23.1
0.23.1.rc1
0.23.2
0.23.3
0.23.4
0.23.5
0.23.6
0.24.0
0.24.0.rc1
0.24.0.rc2
0.24.1
0.24.2
0.24.3
0.25.0
0.25.0.rc1
0.25.0.rc2
0.25.0.rc3
0.25.0.rc4
0.25.1
0.25.2
0.26.0
0.26.0.rc2
0.26.1
0.26.10
0.26.2
0.26.3
0.26.4
0.26.5
0.26.7
0.26.8
0.26.9
0.27.0
0.27.0.rc1
0.27.0.rc2
0.27.1
0.27.10
0.27.2
0.27.3
0.27.4
0.27.5
0.27.6
0.27.7
0.27.8
0.27.9
0.28.0
0.28.0.rc4
0.28.0.rc5
0.28.1
0.28.2
0.28.3
0.28.4
0.28.5
0.28.6
0.29.0
0.29.0.rc1
0.29.0.rc2
0.29.0.rc3
0.29.0.rc4
0.29.1
0.29.2
0.29.3
0.29.4
0.29.5
0.29.6
0.29.7
0.3.0
0.3.1
0.3.2
0.30.0
0.30.0.rc1
0.30.0.rc2
0.30.0.rc3
0.30.1
0.30.2
0.30.3
0.30.4
0.30.5
0.30.6
0.30.7
0.30.8
0.30.9
0.31.0
0.31.0.rc1
0.31.0.rc2
0.31.1
0.31.2
0.31.3
0.31.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.6.5
0.6.6
0.6.7
0.6.8
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.8.0
0.8.1
0.8.2
0.8.3
0.8.4
0.9.0
0.9.1
0.9.2
0.9.3
0.32.0.rc1
0.32.0.rc2
0.32.0.rc3
Fixed in
0.31.5
0.32.0
References Updated Jul 13, 2026 · Source: OSV.dev |
0.28.1
patch
Dependencies (23)
+ 15 more
Changelog
Compare changes
|