CVE-2026-54361

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

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

MISP contained multiple mass assignment vulnerabilities in the handling of collections, tag collections, event delegations, and shadow attributes. Several controller actions accepted user-supplied fields that should have remained server-controlled, including record identifiers and ownership-related fields such as id, org_id, orgc_id, and user_id.

An authenticated attacker with access to the affected endpoints could craft requests containing protected fields in order to alter object ownership, redirect an update to another record, overwrite existing event delegation requests, or modify shadow attribute proposals belonging to another organization. This could result in unauthorized modification of MISP objects and, depending on object visibility and sharing configuration, unauthorized access to or transfer of sensitive threat intelligence data.

The issue was fixed by explicitly pinning ownership and identity fields to their stored values during edit operations and by removing user-supplied primary keys from create-only save paths.

Affected components:

* CollectionsController::edit() * EventDelegationsController::delegateEvent() * ShadowAttributesController::edit() * TagCollectionsController::edit()915 * TagCollectionsController::editWithTags()

Attack requirements: The attacker must be authenticated and able to reach the affected MISP endpoints. No user interaction is required.

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

Published

June 12, 2026

Last Modified

June 15, 2026

Advisory Details (1)

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

commit 9341690e9b6d (MISP/MISP)

Patch available: MISP/MISP v2.5.40 (contains commit 9341690e9b6d)

https://github.com/MISP/MISP/commit/9341690e9b6dde7f0605edea5533e05ba7362e35

Vendor Advisories for CVE-2026-54361(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 14× in last 7d / 79× 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.

Showing the most recent 100 of 134 total refreshes for this CVE.

  1. 2026-07-29 04:17 UTCEG score recompute
  2. 2026-07-29 04:17 UTCGHSA enrichment
  3. 2026-07-28 15:37 UTCEPSS rescore
  4. 2026-07-28 02:04 UTCEG score recompute
  5. 2026-07-28 02:04 UTCGHSA enrichment
  6. 2026-07-27 08:42 UTCGHSA enrichment
  7. 2026-07-26 20:29 UTCEG score recompute
  8. 2026-07-26 20:29 UTCGHSA enrichment
  9. 2026-07-26 14:54 UTCEPSS rescore
  10. 2026-07-25 14:18 UTCEPSS rescore
  11. 2026-07-24 14:18 UTCEPSS rescore
  12. 2026-07-23 14:18 UTCEPSS rescore
  13. 2026-07-23 03:19 UTCEG score recompute
  14. 2026-07-22 14:08 UTCEPSS rescore
  15. 2026-07-20 17:08 UTCEPSS rescore
  16. 2026-07-19 14:31 UTCEPSS rescore
  17. 2026-07-19 14:31 UTCEPSS rescore
  18. 2026-07-19 02:29 UTCEPSS rescore
  19. 2026-07-18 10:04 UTCEPSS rescore
  20. 2026-07-16 23:14 UTCGHSA enrichment
  21. 2026-07-16 17:03 UTCEPSS rescore
  22. 2026-07-16 04:28 UTCGHSA enrichment
  23. 2026-07-15 16:57 UTCEPSS rescore
  24. 2026-07-15 16:57 UTCEPSS rescore
  25. 2026-07-15 16:14 UTCGHSA enrichment
Show 75 more
  1. 2026-07-15 02:00 UTCEPSS rescore
  2. 2026-07-15 02:00 UTCEPSS rescore
  3. 2026-07-15 01:34 UTCGHSA enrichment
  4. 2026-07-14 12:04 UTCGHSA enrichment
  5. 2026-07-13 22:52 UTCGHSA enrichment
  6. 2026-07-13 22:31 UTCEPSS rescore
  7. 2026-07-13 09:50 UTCGHSA enrichment
  8. 2026-07-13 06:13 UTCEPSS rescore
  9. 2026-07-13 06:13 UTCEPSS rescore
  10. 2026-07-12 17:29 UTCGHSA enrichment
  11. 2026-07-12 05:46 UTCEPSS rescore
  12. 2026-07-12 03:29 UTCGHSA enrichment
  13. 2026-07-11 15:07 UTCGHSA enrichment
  14. 2026-07-11 08:27 UTCEPSS rescore
  15. 2026-07-11 08:27 UTCEPSS rescore
  16. 2026-07-11 02:53 UTCGHSA enrichment
  17. 2026-07-10 13:04 UTCGHSA enrichment
  18. 2026-07-09 21:37 UTCGHSA enrichment
  19. 2026-07-09 19:10 UTCEPSS rescore
  20. 2026-07-09 19:10 UTCEPSS rescore
  21. 2026-07-09 03:30 UTCGHSA enrichment
  22. 2026-07-08 15:17 UTCGHSA enrichment
  23. 2026-07-08 15:16 UTCEPSS rescore
  24. 2026-07-08 15:16 UTCEPSS rescore
  25. 2026-07-08 02:13 UTCGHSA enrichment
  26. 2026-07-07 13:59 UTCGHSA enrichment
  27. 2026-07-07 13:46 UTCEPSS rescore
  28. 2026-07-07 13:46 UTCEPSS rescore
  29. 2026-07-07 00:58 UTCGHSA enrichment
  30. 2026-07-06 16:27 UTCEPSS rescore
  31. 2026-07-06 16:27 UTCEPSS rescore
  32. 2026-07-06 02:23 UTCEPSS rescore
  33. 2026-07-06 02:23 UTCEPSS rescore
  34. 2026-07-05 23:16 UTCGHSA enrichment
  35. 2026-07-05 10:57 UTCGHSA enrichment
  36. 2026-07-05 02:31 UTCEPSS rescore
  37. 2026-07-05 02:30 UTCEPSS rescore
  38. 2026-07-04 22:44 UTCGHSA enrichment
  39. 2026-07-04 10:29 UTCGHSA enrichment
  40. 2026-07-04 06:31 UTCEPSS rescore
  41. 2026-07-04 06:31 UTCEPSS rescore
  42. 2026-07-03 19:41 UTCGHSA enrichment
  43. 2026-07-03 07:28 UTCGHSA enrichment
  44. 2026-07-02 17:24 UTCGHSA enrichment
  45. 2026-07-02 05:11 UTCGHSA enrichment
  46. 2026-07-01 16:57 UTCGHSA enrichment
  47. 2026-07-01 15:07 UTCEPSS rescore
  48. 2026-07-01 04:43 UTCGHSA enrichment
  49. 2026-06-30 23:22 UTCEPSS rescore
  50. 2026-06-30 16:17 UTCGHSA enrichment
  51. 2026-06-30 04:00 UTCGHSA enrichment
  52. 2026-06-29 15:47 UTCGHSA enrichment
  53. 2026-06-29 14:06 UTCEPSS rescore
  54. 2026-06-29 14:06 UTCEPSS rescore
  55. 2026-06-29 03:31 UTCGHSA enrichment
  56. 2026-06-28 15:17 UTCGHSA enrichment
  57. 2026-06-28 14:07 UTCEPSS rescore
  58. 2026-06-28 04:56 UTCEPSS rescore
  59. 2026-06-28 04:56 UTCEPSS rescore
  60. 2026-06-28 03:04 UTCGHSA enrichment
  61. 2026-06-27 14:51 UTCGHSA enrichment
  62. 2026-06-27 03:08 UTCEPSS rescore
  63. 2026-06-27 02:38 UTCGHSA enrichment
  64. 2026-06-26 14:25 UTCGHSA enrichment
  65. 2026-06-26 02:11 UTCGHSA enrichment
  66. 2026-06-25 13:56 UTCGHSA enrichment
  67. 2026-06-25 13:49 UTCEPSS rescore
  68. 2026-06-25 01:43 UTCGHSA enrichment
  69. 2026-06-24 14:05 UTCEPSS rescore
  70. 2026-06-24 13:30 UTCGHSA enrichment
  71. 2026-06-24 01:15 UTCGHSA enrichment
  72. 2026-06-23 21:33 UTCEPSS rescore
  73. 2026-06-23 21:33 UTCEPSS rescore
  74. 2026-06-23 13:02 UTCGHSA enrichment
  75. 2026-06-23 00:37 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-54361?
CVE-2026-54361 is a high vulnerability published on June 12, 2026. MISP contained multiple mass assignment vulnerabilities in the handling of collections, tag collections, event delegations, and shadow attributes. Several controller actions accepted user-supplied fields that should have remained server-controlled, including record identifiers and ownership-related…
When was CVE-2026-54361 disclosed?
CVE-2026-54361 was first published in the National Vulnerability Database on June 12, 2026, with the most recent update on June 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54361 actively exploited?
CVE-2026-54361 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 82.1% of all scored CVEs.
What is the CVSS score of CVE-2026-54361?
CVE-2026-54361 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-54361?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54361, 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-54361

Explore →

Is Your Infrastructure Affected by CVE-2026-54361?

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