CVE-2026-104912

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

GHSA-w4mw-2637-h8xp ↗EUVD-2026-91751 ↗

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-862 Missing Authorization
ETK-2026-361, permanent identifier
10d 11h 11msince last run
34mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+205h13m
0
+2h
+4h
+6h
+8h
+10h

description

MISP versions before 2.5.48 can apply outdated access information when resolving correlated data during attribute searches. An authenticated user may view attributes and event metadata from events they can no longer access when relevant correlations exist and an event was later restricted.

mitigation

Upgrade MISP to version 2.5.48 or later. Until upgraded, limit attribute-search access for users who do not require it and review access to recently restricted events.

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.21%10th percentile
agent run time
34m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-02 16:04Z
Δ 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-10-02 16:04Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-361",
  "cve_id": "CVE-2026-104912",
  "display_id": "CVE-2026-104912",
  "ghsa_id": "GHSA-w4mw-2637-h8xp",
  "euvd_id": "EUVD-2026-91751",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authorization bypass in MISP correlation searches",
  "summary": "MISP versions before 2.5.48 can apply outdated access information when resolving correlated data during attribute searches. An authenticated user may view attributes and event metadata from events they can no longer access when relevant correlations exist and an event was later restricted.",
  "mitigation": "Upgrade MISP to version 2.5.48 or later. Until upgraded, limit attribute-search access for users who do not require it and review access to recently restricted events.",
  "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": [
    862
  ],
  "cvss_score": 7.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
  "epss_score": 0.0021,
  "epss_percentile": 0.1021,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 33.6459374,
  "t0_at": "2026-10-02T16:04:50.580000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-02T16:04:50.580000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T16:04:50.580000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-104912"
    }
  }
}

published 2026-10-02 17:38Z
last change 2026-10-21 16:09Z

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.