vault-java-driver: SslConfig silently disables requested TLS verification
- Exploited
- No known exploitation
- Fix
- Fixed in 7.0.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 7.0.0.
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.18% · 7th percentile
- 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? →
- 35/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? →
- Unclear
- 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
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
The vault-java-driver Java client for HashiCorp Vault silently turns off TLS certificate and hostname checks in three configuration cases where verification was requested, so the connection is not authenticated. An attacker on the network path to the Vault server can connect remotely without logging in and read the Vault token and secrets in transit or forge responses, and the bug requires a complex attack setup to succeed.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
vault-java-driver, a Java client for HashiCorp Vault, silently disables TLS certificate and hostname verification in three states where the caller asked for verification: an SslConfig passed to VaultConfig without calling build(), an SslConfig restored by Java deserialization, and VAULT_SSL_VERIFY set to a truthy value other than "true", such as 1, yes or on. In each case SslConfig.isVerify() returns false and the driver installs a trust-all SSLContext. An attacker on the network path to the Vault server can then read the Vault token and secrets in transit and forge responses. This issue affects io.github.jopenlibs:vault-java-driver 5.2.0 through 6.2.3. It is fixed in 7.0.0.
cve.now Index
- Exploitation0/40No signal
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach10/20Affects Maven packages
- Severity8.4/10CVSS 7.4, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 80 if added to CISA KEV
- Would score about 75 if CISA's SSVC rates exploitation active
- Would score about 40 if advisories confirm default setups are exposed
Impact
- Widely used
8 packages depend on io.github.jopenlibs:vault-java-driver.Source: deps.dev
What to do
Upgrade to a fixed version: 7.0.0.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- io.github.jopenlibs:vault-java-driverMaven
From 5.2.0 · fixed in 7.0.0
Evidence 2
- Patch
- Patch
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-109408
Is CVE-2026-109408 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
Which versions are affected by CVE-2026-109408?
io.github.jopenlibs:vault-java-driver (Maven): from 5.2.0 before 7.0.0.Source: cve.now feed data
How do I fix CVE-2026-109408?
Upgrade io.github.jopenlibs:vault-java-driver to 7.0.0 or later.Source: cve.org