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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 11.0.1.2
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Product is IBM Security Verify Directory 10.0.0 through 10.0.4 Product is IBM Verify Directory 11.0.0
- Published
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Read the original 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.8/10CVSS 8.8
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Product is IBM Security Verify Directory 10.0.0 through 10.0.4 Product is IBM Verify Directory 11.0.0Upgrade to a fixed version: 11.0.1.2.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- IBM Security Verify Directory
From 10.0.0 · through 10.0.4
- IBM Verify Directory
11.0.0
Evidence 1
- Patch
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-8639
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: cve.now feed data
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: ibm.com
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: cve.now feed data
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: ibm.com
How do I fix CVE-2026-8639?
Install IBM Verify Directory v11.0.1.2, the fixed version named in the advisory.Source: ibm.com