CVE-2026-103237

waiting for further signalsZero needs more public information before it can validate it.

GHSA-52c6-qg88-jh84 ↗EUVD-2026-89760 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
MISP < 2.5.48
fixed in 2.5.48
CWE-639 Authorization Bypass Through User-Controlled Key
ETK-2026-101, permanent identifier
1d 19h 08msince last run
1h 03mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+457h01m
0
+2h
+4h
+6h
+8h
+10h

description

MISP versions before 2.5.48 mishandle input during ORM-backed save operations across several record types. An authenticated user with perm_add can alter, reassign, or soft-delete records associated with other organizations or events, including records they cannot view.

mitigation

Upgrade MISP to version 2.5.48 or later. Restrict untrusted users from obtaining accounts with write permissions until the update is complete.

fixed in 2.5.48

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.23%12th percentile
agent run time
1h 03m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-30 09:56Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-09-30 09:56Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-103237

{
  "etk_id": "ETK-2026-101",
  "cve_id": "CVE-2026-103237",
  "display_id": "CVE-2026-103237",
  "ghsa_id": "GHSA-52c6-qg88-jh84",
  "euvd_id": "EUVD-2026-89760",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper input validation in MISP ORM save operations",
  "summary": "MISP versions before 2.5.48 mishandle input during ORM-backed save operations across several record types. An authenticated user with perm_add can alter, reassign, or soft-delete records associated with other organizations or events, including records they cannot view.",
  "mitigation": "Upgrade MISP to version 2.5.48 or later. Restrict untrusted users from obtaining accounts with write permissions until the update is complete.",
  "vendor": "MISP",
  "product": "MISP",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 2.5.48"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.5.48"
      ],
      "package_name": "MISP",
      "purl": null
    }
  ],
  "cwes": [
    639
  ],
  "cvss_score": 8.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N",
  "epss_score": 0.0023,
  "epss_percentile": 0.1295,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 62.5009115,
  "t0_at": "2026-09-30T09:56:35.584000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-09-30T09:56:35.584000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-30T09:56:35.584000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-103237"
    }
  }
}

published 2026-09-30 10:45Z
last change 2026-10-21 05:31Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.