CVE-2026-103655

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

GHSA-2hxj-rrwr-5g5v ↗EUVD-2026-90550 ↗

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-294 Authentication Bypass by Capture-replay
ETK-2026-222, permanent identifier
19d 22h 34msince last run
1h 26mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+2h13m
0
+4h
+6h
+8h
+10h
+12h

description

MISP versions before 2.5.48 can accept the same valid TOTP code more than once during its validity period. An attacker who obtains a user's TOTP code during a login may use it to create another authenticated session; the targeted account must have TOTP enabled.

mitigation

Upgrade MISP to version 2.5.48 or later. Until upgraded, reduce opportunities for attackers to observe or intercept TOTP codes and monitor for unexpected account sessions.

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.31%22nd percentile
agent run time
1h 26m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-01 08:08Z
Δ 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-01 08:08Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-222",
  "cve_id": "CVE-2026-103655",
  "display_id": "CVE-2026-103655",
  "ghsa_id": "GHSA-2hxj-rrwr-5g5v",
  "euvd_id": "EUVD-2026-90550",
  "status": "published",
  "anchor_state": "anchored",
  "title": "TOTP code replay in MISP authentication",
  "summary": "MISP versions before 2.5.48 can accept the same valid TOTP code more than once during its validity period. An attacker who obtains a user's TOTP code during a login may use it to create another authenticated session; the targeted account must have TOTP enabled.",
  "mitigation": "Upgrade MISP to version 2.5.48 or later. Until upgraded, reduce opportunities for attackers to observe or intercept TOTP codes and monitor for unexpected account sessions.",
  "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": [
    294
  ],
  "cvss_score": 9.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N",
  "epss_score": 0.0031,
  "epss_percentile": 0.2249,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 85.9178485,
  "t0_at": "2026-10-01T08:08:55.013000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-01T08:08:55.013000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-01T08:08:55.013000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-103655"
    }
  }
}

published 2026-10-01 08:55Z
last change 2026-10-21 07:48Z

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.