CVE-2026-104908

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

GHSA-h9vw-jjgr-29wc ↗EUVD-2026-91745 ↗

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-915 Improperly Controlled Modification of Dynamically-Determined Object Attributes
ETK-2026-363, permanent identifier
18d 16h 16msince last run
32mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+8h17m
0
+2h
+4h
+6h
+10h
+12h

description

MISP versions before 2.5.48 are affected in the decaying-model import feature. An authenticated user granted decaying-model permissions can change existing models across organizational boundaries, including ownership and default-model settings, potentially affecting scoring for other users.

mitigation

Upgrade MISP to version 2.5.48 or later. Until upgraded, remove decaying-model permissions from untrusted accounts and restrict access to the MISP instance.

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.29%19th percentile
agent run time
32m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-02 15: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

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 15:56Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-363",
  "cve_id": "CVE-2026-104908",
  "display_id": "CVE-2026-104908",
  "ghsa_id": "GHSA-h9vw-jjgr-29wc",
  "euvd_id": "EUVD-2026-91745",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper input validation in MISP decaying-model imports",
  "summary": "MISP versions before 2.5.48 are affected in the decaying-model import feature. An authenticated user granted decaying-model permissions can change existing models across organizational boundaries, including ownership and default-model settings, potentially affecting scoring for other users.",
  "mitigation": "Upgrade MISP to version 2.5.48 or later. Until upgraded, remove decaying-model permissions from untrusted accounts and restrict access to the MISP instance.",
  "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": [
    915
  ],
  "cvss_score": 7.1,
  "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:N/SA:N",
  "epss_score": 0.0029,
  "epss_percentile": 0.1996,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 32.064901133333336,
  "t0_at": "2026-10-02T15:56:13.969000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-02T15:56:13.969000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T15:56:13.969000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-104908"
    }
  }
}

published 2026-10-02 17:47Z
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.