CVE-2026-109408: jopenlibs vault-java-driver · Failing Open
Affects jopenlibs vault-java-driverSource CVE Database V5
Not known to be exploited · CVSS 7.4 High : upgrade to 7.0.0 soon.
Data as of 5 Nov 2026, 11:40 UTC
Thin evidence
One scorer or none| CNA (Echo) | CVSS 3.1 | 7.4 |
|---|
- Patch
- Available – fixed in 7.0.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 5 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 5 Nov 2026.
What to do
Upgrade vault-java-driver and io.github.jopenlibs/vault-java-driver to 7.0.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| vault-java-driverio.github.jopenlibs:vault-java-driver | Affected
| Fixed in
|
Mavenio.github.jopenlibs/vault-java-driverpkg:maven/io.github.jopenlibs/vault-java-driverOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade the vault-java-driver to version 7.0.0 or later, where this vulnerability is fixed. Until the upgrade, avoid configurations that trigger the silent disabling of TLS verification, such as passing SslConfig without calling build(), restoring SslConfig via deserialization, or setting VAULT_SSL_VERIFY to values other than "true". No other vendor advisories indicate alternative mitigations.
Description
The vault-java-driver library versions 5.2.0 through 6.2.3 have a vulnerability where TLS certificate and hostname verification can be silently disabled in certain conditions, despite the caller requesting verification. This results in the driver installing a trust-all SSLContext, allowing an attacker on the network path to intercept and read Vault tokens and secrets, and potentially forge responses. The issue is fixed in version 7.0.0.