How severe is GHSA-86fh-w43w-338c?

GHSA-86fh-w43w-338c has a CVSS score of 4.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-86fh-w43w-338c?

GHSA-86fh-w43w-338c affects the following packages: decidim-verifications (RubyGems), decidim-verifications (RubyGems), decidim-verifications (RubyGems). Ecosystems affected: RubyGems.

How do I fix GHSA-86fh-w43w-338c?

Update decidim-verifications to 0.30.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-86fh-w43w-338c is resolved across your whole dependency graph.

How do I detect GHSA-86fh-w43w-338c in my RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for decidim-verifications, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-86fh-w43w-338c if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-86fh-w43w-338c actively exploited in the wild?

No public exploit code has been indexed for GHSA-86fh-w43w-338c yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-86fh-w43w-338c?

GHSA-86fh-w43w-338c has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 38th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-86fh-w43w-338c?

GHSA-86fh-w43w-338c is classified as CWE-639 (CWE-639), CWE-862 (CWE-862). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-86fh-w43w-338c published, and has it been updated?

GHSA-86fh-w43w-338c was published on July 13, 2026 and was last updated on July 13, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💎

💎 RubyGems

Not in CISA KEV

MEDIUM severity

Decidim: Veriﬁcation admins can access supplied IDs from other organizationsGHSA-86fh-w43w-338c

MEDIUMFix: decidim/decidim#16666

GHSA-86fh-w43w-338c is a medium-severity (CVSS 4.9) CWE-639 vulnerability in decidim-verifications. A fix is available for decidim-verifications — see the affected versions and patch details below.

Also known asCVE-2026-45330

Published

Jul 13, 2026

Updated

Jul 13, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Oct 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-86fh-w43w-338c.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs38th percentile — riskier than 38% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-86fh-w43w-338c by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

3 pkgs affected

💎decidim-verifications💎decidim-verifications💎decidim-verifications

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

The verification admin mutation flow allows accessing, verifying, and rejecting participants records from another tenant.

Technical description

The verification admin controllers loads pending_authorization_id with a raw Authorization.find(...) and then authorizes the record without checking whether it belongs to current_organization.

Reproduction steps:

An org2 participant uploads their ID:

An admin from another organisation, in this case org1, is able to open the ID from org2 by opening request 35, e.g http://localhost:3001/admin/id_documents/pending_authorizations/35/confirmations/new

The admin then approves this request by looking up the ID in the picture (not shown in this image, but a real ID would expose this)

Now the request has been approved, which can be seen from the org2 participant authorizations page:

Impact

A tenant admin can access, reject or approve another tenant's id_documents requests.

Patches

See https://github.com/decidim/decidim/pull/16666

Workarounds

Disable the "Identity documents" verification

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.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`decidim-verifications`	all versions	0.30.9`bundle update decidim-verifications --conservative`
💎RubyGems	`decidim-verifications`	≥ 0.31.0.rc1&&< 0.31.5	0.31.5`bundle update decidim-verifications --conservative`
💎RubyGems	`decidim-verifications`	≥ 0.32.0.rc1&&< 0.32.0	0.32.0`bundle update decidim-verifications --conservative`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for decidim-verifications, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update decidim-verifications to 0.30.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-86fh-w43w-338c is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

## Description The verification admin mutation flow allows accessing, verifying, and rejecting participants records from another tenant. ## Technical description The verification admin controllers loads pending_authorization_id with a raw `Authorization.find(...)` and then authorizes the record without checking whether it belongs to current_organization. Reproduction steps: 1. An org2 participant uploads their ID: <img width="2184" height="1288" alt="decidim-verification-01" src="https://github.com/user-attachments/assets/c6713454-c787-4795-b852-3c2c672358d6" /> 2. An admin from another