CVE-2026-8639

validatedZero produced an exploit or a check.

GHSA-x2x7-pqv6-679m ↗EUVD-2026-119734 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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.
IBM Security Verify Directory >= 10.0.0, <= 10.0.4; 11.0.0
CWE-384 Session Fixation
ETK-2026-3910Zero's internal tracking ID, independent of the CVE number., permanent identifier
+1.2dTTV
29mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hcheck available+28h17magent stopped
0
+6h
+12h
+18h
+24h
+30h

description

IBM Security Verify Directory 10.0.0 through 10.0.4 and IBM Verify Directory 11.0.0 are affected by session fixation. An attacker may gain access to the directory management console by taking over a session after a victim authenticates to it. This requires the attacker to establish the session and a victim to authenticate using it.

mitigation

Restrict directory management console access to trusted administrative networks and authorized users to reduce exposure. Consult IBM's advisory or support channel for a corrected release; the available evidence does not name a fixed version.

check
available
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.
deterministic
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%25th percentile
agent run time
29m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-08 18:44Z
Δ 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

Check only, differential: the check fires on the vulnerable build and is silent on the patched one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-08 18:44Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3910",
  "cve_id": "CVE-2026-8639",
  "display_id": "CVE-2026-8639",
  "ghsa_id": "GHSA-x2x7-pqv6-679m",
  "euvd_id": "EUVD-2026-119734",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Session fixation in IBM Security Verify Directory",
  "summary": "IBM Security Verify Directory 10.0.0 through 10.0.4 and IBM Verify Directory 11.0.0 are affected by session fixation. An attacker may gain access to the directory management console by taking over a session after a victim authenticates to it. This requires the attacker to establish the session and a victim to authenticate using it.",
  "mitigation": "Restrict directory management console access to trusted administrative networks and authorized users to reduce exposure. Consult IBM's advisory or support channel for a corrected release; the available evidence does not name a fixed version.",
  "vendor": "IBM",
  "product": "Security Verify Directory",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 10.0.0, <= 10.0.4"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Security Verify Directory",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        "11.0.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Verify Directory",
      "purl": null
    }
  ],
  "cwes": [
    384
  ],
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0032,
  "epss_percentile": 0.2562,
  "epss_asof": "2026-11-09",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 29.031767183333333,
  "t0_at": "2026-11-08T18:44:42.607000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-09T23:02:09.366844+00:00",
      "days": 1.1787819426388888,
      "is_lower_bound": false,
      "measured_at": "2026-11-08T18:44:42.607000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-11-08T18:44:42.607000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-08T18:44:42.607000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-8639"
    }
  }
}

published 2026-11-08 19:06Z
last change 2026-11-11 05: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.