CVE-2026-103321

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

GHSA-w4mv-4x7w-vpvv ↗EUVD-2026-89800 ↗

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-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
ETK-2026-118, permanent identifier
20d 08h 55msince last run
11mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+11h40m
0
+2h
+4h
+6h
+8h
+10h

description

MISP versions before 2.5.48 can retain unsafe event graph preview image data. An authenticated user able to edit event graph entries may cause script to run in another user's MISP session when that user opens the preview.

mitigation

Upgrade MISP to version 2.5.48 or later. Until upgraded, restrict event graph editing to trusted users and avoid opening previews from untrusted entries.

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.
contextual
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.36%28th percentile
agent run time
11m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-30 12:19Z
Δ 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

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-118",
  "cve_id": "CVE-2026-103321",
  "display_id": "CVE-2026-103321",
  "ghsa_id": "GHSA-w4mv-4x7w-vpvv",
  "euvd_id": "EUVD-2026-89800",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Stored cross-site scripting in MISP event graph previews",
  "summary": "MISP versions before 2.5.48 can retain unsafe event graph preview image data. An authenticated user able to edit event graph entries may cause script to run in another user's MISP session when that user opens the preview.",
  "mitigation": "Upgrade MISP to version 2.5.48 or later. Until upgraded, restrict event graph editing to trusted users and avoid opening previews from untrusted entries.",
  "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": [
    79
  ],
  "cvss_score": 8.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:H/VA:N/SC:H/SI:H/SA:N",
  "epss_score": 0.0036,
  "epss_percentile": 0.2831,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 10.821183883333333,
  "t0_at": "2026-09-30T12:19:01.829000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-09-30T12:19:01.829000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-30T12:19:01.829000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-103321"
    }
  }
}

published 2026-09-30 14:49Z
last change 2026-10-21 04:45Z

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.