Skip to main content
VulnerabilityPublished Updated

CVE-2026-8715: HashiCorp Tooling · Exposed Files or Directories

Affects HashiCorp ToolingSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.6 Critical : upgrade to 1.5.0 as a priority.

Data as of 10 Nov 2026, 23:24 UTC

CVSS 3.1 base score
9.6Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.5.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 11 Nov 2026.

What to do

Upgrade HashiCorp Tooling to 1.5.0.

Affected software

ProductAffectedFixed in
HashiCorpToolingAffected
  • >=1.3.0 <1.5.0
Fixed in
  • 1.5.0
GitHubToolingpkg:github/ToolingOther threatsAffected
  • >=1.3.0 <1.5.0
Fixed in
  • 1.5.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Vault Secrets Operator to version 1.5.0 or later, where this vulnerability is fixed. No other mitigations are specified in the vendor advisory.

Description

Vault Secrets Operator versions 1.3.0 through 1.4.1 contain a vulnerability in the AppRole authentication configuration that allows tenants with limited Kubernetes RBAC permissions to read arbitrary files from the operator pod's filesystem and exfiltrate credentials. This can lead to privilege escalation within the Kubernetes cluster. The issue is fixed in version 1.5.0.

References

Community reviews

Loading reviews…