IBM Security Verify Directory 10.0.0 through 10.0.4 and IBM Verify Directory 11.0.0 does not set the SameSite
Source GCVE Database
Not known to be exploited · CVSS 3.5 Low.
Data as of 9 Nov 2026, 00:20 UTC
Thin evidence
One scorer or none| CNA (ibm) | CVSS 3.1 | 3.5 |
|---|
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 8 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IBMSecurity Verify Directory | Affected
| Fixed in– |
| IBMVerify Directory | Affected
| Fixed in– |
AI-suggested
Since the SameSite attribute is a cookie configuration, administrators should consider configuring session cookies to include the SameSite attribute to mitigate CSRF risks. Monitor vendor advisories for any official updates or patches.
Description
IBM Security Verify Directory versions 10.0.0 through 10.0.4 and 11.0.0 do not set the SameSite attribute on session cookies. This omission makes the application vulnerable to Cross-Site Request Forgery (CSRF) attacks, where an attacker could trick authenticated users into sending unauthorized requests. The vulnerability has a low severity score and does not impact confidentiality or availability.