Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-45378 high CVSS 7.5

Information Disclosure in decidim-verifications (CVE-2026-45378)

Summary

Vulnerability in decidim-verifications (CVE-2026-45378). Confidential information can be exposed externally. Exploitable via verification_attachment. Mitigation: upgrade to 0.32.0 or later.

Original description

The description as published by the source.

Description

Scanned identity-document images provided by participants and shown in the verification admin workflow are exposed through signed /rails/active_storage/disk/ URLs that can be fetched without any authenticated session.

Anyone who obtains one of those URLs can retrieve the document until the signature expires.

Technical description

This issue comes from the verification admin UI exposing scanned documents through reusable Active Storage disk links. Verification-document images are rendered with variant_url(...), which produces signed /rails/active_storage/disk/... links instead of routing the file through an authorization-checking controller. Because Decidim configures Active Storage service URLs to remain valid for seven days, the URL itself becomes the credential for that period.

The affected files are verification_attachment blobs on Decidim::Authorization, and the admin review pages embed those signed URLs directly into the HTML for pending and confirmation views.

Reproduction steps:

  1. Create a fresh verification document as a normal user.
    1.1. Open http://localhost:3001/users/sign_in.
    1.2. Open http://localhost:3001/id_documents/authorizations/new.
    1.3. Submit an id_documents verification request with an image attachment.

  2. Open the admin review page that renders the attachment.
    2.1. Sign out.
    2.2. Sign back in as admin@example.org.
    2.3. Try http://localhost:3001/admin/id_documents.

  3. Harvest the signed Active Storage URL.
    3.1. Open De…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-45378 has been found in decidim-verifications.
Attackers can target a specific entry point like verification_attachment over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade decidim-verifications to 0.32.0 or later.
If unsure, ask your IT team or search "decidim-verifications CVE-2026-45378" on the vendor's site.

CVE-2026-45378 (decidim-verifications) — CWE-200 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: verification_attachment
Patched: 0.32.0 — apply immediately
Workaround: Disable the "Identity documents" verification
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Information disclosure (CWE-200) exists in decidim-verifications. Attackers reach the vulnerable code path via verification_attachment without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of decidim-verifications. Attack surface: verification_attachment.

🔥 Severity

Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 0.32.0.

🛡️ Workaround

Workaround: Disable the "Identity documents" verification

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'decidim-verifications' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'decidim-verifications' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で decidim-verifications を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    Disable the "Identity documents" verification

    パッチが適用されるまでの応急処置として、Disable the "Identity documents" verification を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade decidim-verifications to 0.32.0

    ステージング環境で 0.32.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

rubygems decidim-verifications
[{"type":"ECOSYSTEM","events":[{"introduced":"0.32.0.rc1"},{"fixed":"0.32.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details