CVE-2026-107180

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

GHSA-jgf2-xf9x-w72j ↗EUVD-2026-94318 ↗

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-287 Improper Authentication
ETK-2026-872, permanent identifier
9d 06h 30msince last run
15mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+105h30m
0
+2h
+4h
+6h
+8h
+10h

description

MISP versions earlier than 2.5.48 can fail to enforce required TOTP enrollment for certain authenticated, non-browser requests. An authenticated user who has not enrolled in TOTP may continue using the instance when the Security.otp_required setting is enabled.

mitigation

Upgrade MISP to version 2.5.48 or later. Until upgraded, restrict non-browser access for accounts that have not completed TOTP enrollment.

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.32%22nd percentile
agent run time
15m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-07 12:49Z
Δ 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-07 12:49Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-872",
  "cve_id": "CVE-2026-107180",
  "display_id": "CVE-2026-107180",
  "ghsa_id": "GHSA-jgf2-xf9x-w72j",
  "euvd_id": "EUVD-2026-94318",
  "status": "published",
  "anchor_state": "anchored",
  "title": "TOTP enrollment enforcement bypass in MISP",
  "summary": "MISP versions earlier than 2.5.48 can fail to enforce required TOTP enrollment for certain authenticated, non-browser requests. An authenticated user who has not enrolled in TOTP may continue using the instance when the Security.otp_required setting is enabled.",
  "mitigation": "Upgrade MISP to version 2.5.48 or later. Until upgraded, restrict non-browser access for accounts that have not completed TOTP enrollment.",
  "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": [
    287
  ],
  "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.0032,
  "epss_percentile": 0.2296,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 15.000219966666666,
  "t0_at": "2026-10-07T12:49:40.483000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-07T12:49:40.483000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-07T12:49:40.483000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-107180"
    }
  }
}

published 2026-10-07 13:51Z
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.