CVE-2026-45376

MEDIUMPre-NVD 5.55.5
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 73% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Decidim is a participatory democracy framework. Prior to 0.30.9, from 0.31.0 before 0.31.5, and in 0.32.0.rc1 before 0.32.0.rc2, the GET /admin/organization/users search interpolates params[:term] into raw Arel.sql ORDER BY similarity expressions before sanitization, allowing an authenticated organization administrator to execute blind PostgreSQL expressions and infer data through timing differences. This issue is fixed in versions 0.30.9, 0.31.5, and 0.32.0.rc2.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
41(Track)
EG Risk 41/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

July 13, 2026

Last Modified

August 3, 2026

Advisory Details (7)

Auto-updated Jul 31, 2026
Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

Release v0.32.0.rc2 (decidim/decidim)

Patch available: decidim/decidim v0.32.0.rc2 (pre-release)

https://github.com/decidim/decidim/releases/tag/v0.32.0.rc2
github_release Patch Available

Release v0.31.5 (decidim/decidim)

Patch available: decidim/decidim v0.31.5

https://github.com/decidim/decidim/releases/tag/v0.31.5
github_release Patch Available

Release v0.30.9 (decidim/decidim)

Patch available: decidim/decidim v0.30.9

https://github.com/decidim/decidim/releases/tag/v0.30.9
github_commit

commit f3817fac448a (decidim/decidim)

Fix landed in decidim/decidim commit f3817fac448a — awaiting tagged release

https://github.com/decidim/decidim/commit/f3817fac448a4e3facd6bcb346167048b3421124
github_commit

commit e4d21b41fb46 (decidim/decidim)

Fix landed in decidim/decidim commit e4d21b41fb46 — awaiting tagged release

https://github.com/decidim/decidim/commit/e4d21b41fb462d9436035a043962a4090f2cc240
github_commit

commit 27335957b363 (decidim/decidim)

Fix landed in decidim/decidim commit 27335957b363 — awaiting tagged release

https://github.com/decidim/decidim/commit/27335957b363516e23919a9006812f1c458c88e0
github Patch Available

Admin user search allows SQL injection through similarity-based sorting · Advisory · decidim/decidim · GitHub

https://github.com/decidim/decidim/security/advisories/GHSA-jvqq-cvh4-xm37

Vendor Advisories for CVE-2026-45376(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
RubyGems(1)
PackageVulnerable rangeFixed inDependents
decidim-admin0.32.0.rc1, 0.32.0.rc2, 0.32.0.rc30.32.0

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 53× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 05:29 UTCEG score recompute
  2. 2026-08-30 01:22 UTCEPSS rescore
  3. 2026-08-28 21:41 UTCEPSS rescore
  4. 2026-08-27 14:25 UTCEPSS rescore
  5. 2026-08-27 14:16 UTCEG score recompute
  6. 2026-08-26 14:46 UTCEPSS rescore
  7. 2026-08-26 12:51 UTCEG score recompute
  8. 2026-08-25 13:49 UTCEPSS rescore
  9. 2026-08-25 10:57 UTCEG score recompute
  10. 2026-08-23 06:03 UTCEG score recompute
  11. 2026-08-23 00:19 UTCEPSS rescore
  12. 2026-08-22 04:39 UTCEG score recompute
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-21 02:37 UTCEG score recompute
  15. 2026-08-20 22:55 UTCEPSS rescore
  16. 2026-08-20 01:13 UTCEG score recompute
  17. 2026-08-19 17:04 UTCEPSS rescore
  18. 2026-08-18 20:26 UTCEG score recompute
  19. 2026-08-18 13:48 UTCEPSS rescore
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-17 13:02 UTCEG score recompute
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 11:38 UTCEG score recompute
  24. 2026-08-16 02:14 UTCEPSS rescore
  25. 2026-08-15 10:15 UTCEG score recompute
Show 32 more
  1. 2026-08-15 01:30 UTCEPSS rescore
  2. 2026-08-14 08:51 UTCEG score recompute
  3. 2026-08-13 22:00 UTCEPSS rescore
  4. 2026-08-13 07:27 UTCEG score recompute
  5. 2026-08-12 13:51 UTCEPSS rescore
  6. 2026-08-12 05:57 UTCEG score recompute
  7. 2026-08-11 04:33 UTCEG score recompute
  8. 2026-08-11 00:00 UTCEPSS rescore
  9. 2026-08-10 03:09 UTCEG score recompute
  10. 2026-08-09 13:46 UTCEPSS rescore
  11. 2026-08-09 01:46 UTCEG score recompute
  12. 2026-08-08 16:37 UTCEPSS rescore
  13. 2026-08-08 00:22 UTCEG score recompute
  14. 2026-08-06 22:59 UTCEG score recompute
  15. 2026-08-06 13:47 UTCEPSS rescore
  16. 2026-08-05 21:06 UTCEG score recompute
  17. 2026-08-05 19:17 UTCEPSS rescore
  18. 2026-08-04 19:42 UTCEG score recompute
  19. 2026-08-04 15:10 UTCEPSS rescore
  20. 2026-08-04 10:38 UTCEPSS rescore
  21. 2026-08-03 18:18 UTCEG score recompute
  22. 2026-08-03 18:05 UTCEG score recompute
  23. 2026-08-03 10:36 UTCEPSS rescore
  24. 2026-08-03 02:20 UTCEG score recompute
  25. 2026-08-02 02:27 UTCEPSS rescore
  26. 2026-07-31 23:32 UTCEG score recompute
  27. 2026-07-31 22:48 UTCEG score recompute 1.30
  28. 2026-07-31 22:48 UTCMITRE cvelistV5CVSS v3 → 5.5
  29. 2026-07-30 17:38 UTCEG score recompute
  30. 2026-07-26 11:53 UTCEG score recompute
  31. 2026-07-23 03:16 UTCEG score recompute
  32. 2026-07-13 17:08 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-45376?
CVE-2026-45376 is a medium vulnerability published on July 13, 2026. Decidim is a participatory democracy framework. Prior to 0.30.9, from 0.31.0 before 0.31.5, and in 0.32.0.rc1 before 0.32.0.rc2, the GET /admin/organization/users search interpolates params[:term] into raw Arel.sql ORDER BY similarity expressions before sanitization, allowing an authenticated…
When was CVE-2026-45376 disclosed?
CVE-2026-45376 was first published in the National Vulnerability Database on July 13, 2026, with the most recent update on August 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45376 actively exploited?
CVE-2026-45376 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 73.2% of all scored CVEs.
What is the CVSS score of CVE-2026-45376?
CVE-2026-45376 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-45376?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45376, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45376

Explore →

Is Your Infrastructure Affected by CVE-2026-45376?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.