What is CVE-2026-45415?

CVE-2026-45415 is a medium-severity security vulnerability in decidim-verifications (rubygems), affecting versions < 0.30.9. It is fixed in 0.30.9, 0.31.5, 0.32.0.

How severe is CVE-2026-45415?

CVE-2026-45415 has a CVSS score of 6.0 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of decidim-verifications are affected by CVE-2026-45415?

decidim-verifications (rubygems) versions < 0.30.9 is affected.

Is there a fix for CVE-2026-45415?

Yes. CVE-2026-45415 is fixed in 0.30.9, 0.31.5, 0.32.0. Upgrade to this version or later.

Is CVE-2026-45415 exploitable, and should I be worried?

Whether CVE-2026-45415 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-45415 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-45415?

Upgrade: decidim-verifications to 0.30.9 or later, decidim-verifications to 0.31.5 or later, decidim-verifications to 0.32.0 or later.

CVE-2026-45415 in decidim-verifications

Q: How severe is CVE-2026-45415?

CVE-2026-45415 has a CVSS score of 6.0 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of decidim-verifications are affected by CVE-2026-45415?

decidim-verifications (rubygems) versions < 0.30.9 is affected.

Q: Is there a fix for CVE-2026-45415?

Yes. CVE-2026-45415 is fixed in 0.30.9, 0.31.5, 0.32.0. Upgrade to this version or later.

Q: Is CVE-2026-45415 exploitable, and should I be worried?

Whether CVE-2026-45415 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-45415 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-45415?

Upgrade: decidim-verifications to 0.30.9 or later, decidim-verifications to 0.31.5 or later, decidim-verifications to 0.32.0 or later.

Summary

Decidim: CSV census record endpoints improper authorization

Description

A participant manager can access and modify the CSV census record admin forms.

Technical description

The CSV census admin record-management surface under /admin/csv_census/census_logs does not enforce admin-only authorization before rendering or mutating Decidim::Verifications::CsvDatum.

A participant manager (which can only manage participants) can therefore open the admin forms, create or update census rows, and delete rows directly.

Reproduction steps:

Sign in a participant admin and open http://localhost:3000/admin/csv_census/census_logs/new_record in the browser. Confirm the create form loads even though the session is not a full admin.

Note that normal participant accounts were not able to access the CSV census records which is good.

Workarounds

Disable Organization Census verification method

Reference

OWASP A01:2021 Broken Access Control

Credits

This issue was discovered in a security audit organized by the Decidim Association and made by Radically Open Security against Decidim financed by NGI.

Impact

Any participant admin can create, alter, or remove CSV census rows, which can corrupt verification data relied on by authorization workflows.

CVE-2026-45415 has a CVSS score of 6.0 (Medium). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.30.9, 0.31.5, 0.32.0); upgrading removes the vulnerable code path.

Affected versions

decidim-verifications (< 0.30.9) decidim-verifications (>= 0.31.0.rc1, < 0.31.5) decidim-verifications (>= 0.32.0.rc1, < 0.32.0)

Security releases

decidim-verifications → 0.30.9 (rubygems) decidim-verifications → 0.31.5 (rubygems) decidim-verifications → 0.32.0 (rubygems)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

See https://github.com/decidim/decidim/pull/16674 and https://github.com/decidim/decidim/pull/16703

Frequently Asked Questions

What is CVE-2026-45415? CVE-2026-45415 is a medium-severity security vulnerability in decidim-verifications (rubygems), affecting versions < 0.30.9. It is fixed in 0.30.9, 0.31.5, 0.32.0.
How severe is CVE-2026-45415? CVE-2026-45415 has a CVSS score of 6.0 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of decidim-verifications are affected by CVE-2026-45415? decidim-verifications (rubygems) versions < 0.30.9 is affected.
Is there a fix for CVE-2026-45415? Yes. CVE-2026-45415 is fixed in 0.30.9, 0.31.5, 0.32.0. Upgrade to this version or later.
Is CVE-2026-45415 exploitable, and should I be worried? Whether CVE-2026-45415 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-45415 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-45415?
- Upgrade decidim-verifications to 0.30.9 or later
- Upgrade decidim-verifications to 0.31.5 or later
- Upgrade decidim-verifications to 0.32.0 or later

Other vulnerabilities in decidim-verifications

CVE-IDSeverityPackage summary

CVE-2026-45378Highdecidim-verifications: Decidim: Verification documents can be downloaded through reusable links CVE-2026-45330Mediumdecidim-verifications: Decidim: Veriﬁcation admins can access supplied IDs from other organizations