{
  "id": "CVE-2026-103655",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-103655",
  "published_at": "2026-10-01T08:08:55.013Z",
  "title": "MISP TOTP Code Replay Allows Duplicate Authentication Within Validity Period",
  "vendor": "MISP",
  "product": "MISP",
  "cvss": {
    "score": 9.3,
    "source": "cna",
    "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"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "MISP contains a vulnerability in its two-factor authentication (TOTP) verification process that permits a valid one-time code to be accepted more than once within its time-based validity window.\n\nThe issue exists in the user login flow where a TOTP code is verified as a second authentication factor. Because the system did not record whether a given TOTP period had already been consumed, the same code remained valid for its entire time window (typically 30 seconds). An attacker who captures a legitimate code during a user's login could replay it to authenticate a second session as that user.\n\nPreconditions:\n\n- The target user has TOTP-based two-factor authentication enabled.\n\n- The attacker is in a position to observe or intercept the TOTP code during a legitimate login (e.g., network-level interception, shoulder surfing, or a compromised client).\n\n- The replay must occur within the TOTP validity period.\n\nSecurity impact:\n\n- Unauthorized account access by replaying a captured one-time code.\n\n- Potential compromise of threat-intelligence data and administrative functions accessible to the targeted user.\n\nAffected versions: \u003cv2.5.48.",
  "cwe": "CWE-294",
  "cvss_by_source": {
    "cna": 9.3
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "MISP",
        "product": "MISP",
        "ranges": [
          "\u003c 2.5.48"
        ],
        "fixed_in": [
          "2.5.48"
        ]
      }
    ],
    "solutions": [
      "The fix introduces a single-use enforcement mechanism for TOTP codes. Upon successful verification, the system records the TOTP period step in a Redis key scoped to the user and step number, using a SET-NX (set-if-not-exists) operation with a TTL of three times the TOTP period. Any subsequent attempt to authenticate with a code from the same period will fail the SET-NX check and be rejected, effectively making each TOTP code single-use within its validity window."
    ],
    "upgrade": [
      "Upgrade MISP to 2.5.48 or later."
    ],
    "references": [
      {
        "kind": "Patch",
        "url": "https://github.com/MISP/MISP/commit/a020fa47b"
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
