← Back
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.
AI summary snake-internal / snake-material-v2
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
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 (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'decidim-verifications' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `decidim-verifications` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Disable the "Identity documents" verificationパッチが適用されるまでの応急処置として、Disable the "Identity documents" verification を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade decidim-verifications to 0.32.0ステージング環境で 0.32.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
rubygems
decidim-verifications
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.32.0"}]}]