GITHUB-ACTIONS · JULY 2026 · EARLY WARNING

Decidim Package Authorization Issue: Potential Data Corruption Risk

EARLY WARNING · UNCONFIRMED. This page describes a developing threat that 0Day surfaced from early signals and has not yet independently confirmed. Details may change. Always verify against the primary sources before acting.
GHSA-Q79H-67VX-M9XGSeverity: HIGH

An issue has been reported in the Decidim package where participant managers may be able to access and modify CSV census records without proper authorization. This could potentially lead to corruption of verification data used in authorization workflows.

What happened

Reportedly, the Decidim package contains an improper authorization vulnerability in its CSV census record endpoints. This vulnerability appears to allow participant managers to access and modify census records without the necessary permissions. As a result, there is a risk that verification data used in authorization workflows could be corrupted. The issue is currently under investigation and more details should be obtained from the primary sources. To assess your exposure, check if your systems use Decidim for managing participant data and consider upgrading to a version that includes the necessary authorization fixes, such as those in pull requests 16674 and 16703.

How 0Day mitigates this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If decidim is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Join the 0Day waitlist →

← Back to all threats