CVE-2026-91825

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 70% 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
Trending — 3 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

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

Affected versions of MISP fail to authorize a submitted sharing group in a specific event-edit path.

The vulnerable logic checked whether the acting user could use a sharing_group_id only when the request explicitly supplied distribution = 4. If the attacker instead omitted distribution but supplied a different sharing_group_id, that authorization branch was skipped. Later, MISP’s field-recovery logic restored the existing event distribution from storage. For events already configured with sharing-group distribution, the unauthorized sharing-group ID could therefore be saved.

The fix adds authorization checks in both the controller and Event::_edit() whenever a non-empty sharing_group_id is supplied without distribution. The model now calls SharingGroup::checkIfAuthorised() before persisting the change.

Version affected: ≤2.5.45

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
32(Track)
EG Risk 32/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
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

Published

September 15, 2026

Last Modified

September 16, 2026

Advisory Details (1)

Auto-updated Sep 15, 2026
Patch available. Sources: github_commit.
github_commit Patch Available

commit cf3ee4026 (MISP/MISP)

Patch available: MISP/MISP v2.5.46 (contains commit cf3ee4026)

https://github.com/MISP/MISP/commit/cf3ee4026

Vendor Advisories for CVE-2026-91825(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 27× in last 7d / 45× 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-09-25 08:29 UTCGHSA enrichment
  2. 2026-09-24 20:07 UTCEG score recompute
  3. 2026-09-24 20:07 UTCGHSA enrichment
  4. 2026-09-24 14:04 UTCEPSS rescore
  5. 2026-09-24 07:44 UTCGHSA enrichment
  6. 2026-09-23 19:22 UTCEG score recompute
  7. 2026-09-23 19:22 UTCGHSA enrichment
  8. 2026-09-23 17:54 UTCEPSS rescore
  9. 2026-09-23 06:43 UTCGHSA enrichment
  10. 2026-09-22 18:21 UTCEG score recompute
  11. 2026-09-22 18:21 UTCGHSA enrichment
  12. 2026-09-22 16:01 UTCEPSS rescore
  13. 2026-09-22 05:57 UTCEG score recompute
  14. 2026-09-22 05:57 UTCGHSA enrichment
  15. 2026-09-21 21:09 UTCEPSS rescore
  16. 2026-09-21 17:35 UTCGHSA enrichment
  17. 2026-09-21 05:10 UTCEG score recompute
  18. 2026-09-21 05:09 UTCGHSA enrichment
  19. 2026-09-20 20:16 UTCEPSS rescore
  20. 2026-09-20 16:47 UTCGHSA enrichment
  21. 2026-09-20 04:23 UTCGHSA enrichment
  22. 2026-09-19 16:00 UTCEG score recompute
  23. 2026-09-19 16:00 UTCGHSA enrichment
  24. 2026-09-19 03:37 UTCEG score recompute
  25. 2026-09-19 03:37 UTCGHSA enrichment
Show 20 more
  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 15:15 UTCGHSA enrichment
  3. 2026-09-18 02:52 UTCEG score recompute
  4. 2026-09-18 02:52 UTCGHSA enrichment
  5. 2026-09-17 19:32 UTCEPSS rescore
  6. 2026-09-17 14:30 UTCGHSA enrichment
  7. 2026-09-17 02:07 UTCEG score recompute
  8. 2026-09-17 02:07 UTCGHSA enrichment
  9. 2026-09-16 14:09 UTCEPSS rescore
  10. 2026-09-16 13:44 UTCEG score recompute
  11. 2026-09-16 13:44 UTCGHSA enrichment
  12. 2026-09-16 05:15 UTCEPSS rescore
  13. 2026-09-16 03:55 UTCGHSA enrichment
  14. 2026-09-15 15:31 UTCEG score recompute
  15. 2026-09-15 15:31 UTCGHSA enrichment
  16. 2026-09-15 14:33 UTCEG score recompute
  17. 2026-09-15 14:33 UTCGHSA enrichment
  18. 2026-09-15 09:27 UTCEG score recompute
  19. 2026-09-15 08:33 UTCEG score recompute
  20. 2026-09-15 08:32 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-91825?
CVE-2026-91825 is a high vulnerability published on September 15, 2026. Affected versions of MISP fail to authorize a submitted sharing group in a specific event-edit path. The vulnerable logic checked whether the acting user could use a sharinggroupid only when the request explicitly supplied distribution = 4. If the attacker instead omitted distribution but supplied…
When was CVE-2026-91825 disclosed?
CVE-2026-91825 was first published in the National Vulnerability Database on September 15, 2026, with the most recent update on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-91825 actively exploited?
CVE-2026-91825 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 69.8% of all scored CVEs.
What is the CVSS score of CVE-2026-91825?
CVE-2026-91825 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-91825?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-91825, 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

Explore the affected products and dependency analysis for CVE-2026-91825

Explore →

Is Your Infrastructure Affected by CVE-2026-91825?

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