/

CVE-2026-45378

Severity:

HIGH RISK

(7.5)

Sensitive Data Exposure (CWE-200) in Decidim Admin UI

CVE-2026-45378

Received

Vulnerability type

Category:

Sensitive Data Exposure

CWE:

CWE-200

Impact:

Unauthorized Disclosure of Sensitive Identity Documents

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Decidim exposes identity-verification documents through signed Active Storage URLs embedded in administrative review pages. Anyone who obtains one of these URLs may download the associated scanned document without an authenticated Decidim session until the URL signature expires.

Affected context

The issue occurs in Decidim deployments where identity-document verification attachments are displayed through Active Storage variant URLs. These URLs point directly to disk-serving endpoints rather than an application controller that performs authorization checks, and the URL remains usable for the configured service lifetime. Pending and confirmation review pages may therefore expose verification-document links in rendered HTML.

Exploit preconditions

  • Attack surface: Decidim administrative verification-review pages and generated HTML
  • Required access: Ability to obtain or observe a signed document URL; an authenticated Decidim session is not required to use the URL afterward
  • Trigger point: A request to the signed Active Storage disk URL before its signature expires
  • Why exploitation is possible: The reusable signed URL acts as the bearer credential and is not revalidated against the user's Decidim authorization when the document is downloaded

Why this happens

The underlying issue is an authorization-bypass pattern in which a sensitive blob is exposed through a bearer-style storage URL instead of an authorization-enforcing application endpoint. Although the URL is signed, possession of a valid signature is sufficient to retrieve the document for its lifetime. This maps to CWE-200: Exposure of Sensitive Information to an Unauthorized Actor, because identity documents can be disclosed outside the intended administrative access boundary.

Potential impact

  • Unauthorized download of scanned identity documents
  • Exposure of personally identifiable information
  • Privacy violations affecting verification applicants
  • Further sharing or indexing of valid document URLs
  • Regulatory, legal, or reputational consequences

General mitigation guidance

Mitigation generally focuses on preserving authorization checks throughout the document-delivery path and reducing the value of leaked URLs.

Common defensive patterns include:

  • Serving sensitive attachments through controllers or services that verify authorization for every request
  • Avoiding direct, reusable storage URLs in HTML for protected documents
  • Using short-lived, narrowly scoped, and revocable access grants where direct delivery is unavoidable
  • Preventing sensitive URLs from appearing in logs, referrers, caches, and client-visible markup when possible
  • Applying least-privilege access to document storage and administrative review functions
  • Treating verification attachments as sensitive data and enforcing retention, access, and audit policies

How teams detect issues like this

Organizations can assess this class of issue through:

  • Static analysis and code review searches for direct blob URLs, variant URL helpers, and storage endpoints used with sensitive records
  • Review of whether file-download controllers perform record-level authorization before redirecting or streaming content
  • Dynamic tests that request previously captured document URLs without an authenticated application session
  • Proxy and web-server log analysis for document downloads that lack corresponding authorized review activity
  • Policy checks requiring sensitive files to use authorization-aware delivery paths and short-lived access controls

Automated security review tools may help identify direct storage-link generation, but authorization behavior should also be verified with integration tests.

Sources

SourceLink
github.comgithub.com/decidim/decidim/security/advisories/GHSA-3mvf-82qp-8qh5

Frequently asked

questions

Yes. An attacker who obtains a valid signed document URL may request it remotely without maintaining an authenticated Decidim session, provided the signature has not expired.

Not necessarily. The key requirement is obtaining or observing a signed URL, which may be exposed through rendered HTML, logs, browser history, referrers, or other handling of the administrative page.

Deliver sensitive verification documents through an authorization-aware endpoint that checks the current user's permission for every request, rather than relying solely on a reusable storage signature.

Classify identity documents as sensitive, test direct storage URLs without session credentials, minimize URL lifetime and exposure, and enforce review-page and download authorization through automated tests and policy checks.

Find out what's already
exploitable in your codebase.