CVE-2026-8715: Vault Secrets Operator vulnerable to arbitrary file read and credential exfiltration via AppRole secretIDPath
Vault Secrets Operator 1.3.0 up to 1.4.1 is vulnerable to an arbitrary file read and credential exfiltration issue in the AppRole authentication configuration that may allow a tenant with limited Kubernetes RBAC permissions to read files from the operator pod's filesystem and transmit their contents to a tenant-controlled endpoint, potentially leading to privilege escalation within the cluster. This vulnerability (CVE-2026-8715) is fixed in Vault Secrets Operator 1.5.0.
Security readout for executives and security teams
Plain-English summary
A tenant with limited Kubernetes permissions may abuse Vault Secrets Operator’s AppRole configuration to read files from the operator pod and send sensitive contents outside the cluster. Stolen credentials could enable broader cluster access. Versions 1.3.0 through 1.4.1 are affected; version 1.5.0 fixes the issue.
Executive priority
Prioritize immediate remediation for affected multi-tenant or shared clusters because limited tenant permissions may become credential theft and cluster privilege escalation. Upgrade to 1.5.0 promptly. For isolated deployments without untrusted tenants or relevant configuration access, validate exposure quickly and schedule remediation according to confirmed reachability.
Technical view
CVE-2026-8715 affects Vault Secrets Operator AppRole authentication through secretIDPath. A low-privileged tenant may cause arbitrary files from the operator pod filesystem to be read and transmitted to a tenant-controlled endpoint. The cross-boundary impact can expose credentials and enable privilege escalation. CVSS 3.1 is 9.6, with high confidentiality and integrity impact but no stated availability impact.
Likely exposure
Exposure requires Vault Secrets Operator versions 1.3.0 through 1.4.1 and tenant access sufficient to configure the vulnerable AppRole authentication path. Risk is greatest in multi-tenant clusters where limited-RBAC tenants share an operator containing valuable credentials. The bundle does not define the exact Kubernetes permissions required.
Exploitation context
The supplied record is not marked as CISA KEV and provides no evidence of active exploitation. Exploitation is described as network-accessible, low complexity, requiring low privileges, and needing no user interaction. Treat this as a high-impact privilege-boundary weakness, not proof that attacks are occurring.
Researcher notes
The source bundle identifies secretIDPath as the vulnerable AppRole input and arbitrary operator-pod file disclosure with outbound exfiltration as the core behavior. Exact RBAC prerequisites, readable file boundaries, runtime safeguards, indicators of compromise, and proof-of-concept availability are not provided. Validate those details against HashiCorp’s advisory without testing against production systems.
Mitigation direction
Upgrade Vault Secrets Operator to version 1.5.0 or later.
Prioritize multi-tenant clusters where tenants can configure AppRole authentication.
Review and minimize tenant RBAC access to Vault Secrets Operator resources.
Check HashiCorp’s advisory for any additional containment guidance.
Validation and detection
Inventory Vault Secrets Operator deployments and record their running versions.
Confirm all deployments run version 1.5.0 or later.
Identify tenants permitted to create or modify AppRole authentication configuration.
Review operator pod access, credentials, and outbound connections for unexpected activity.
Verify RBAC prevents unnecessary tenant modification of operator authentication resources.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-552: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
2ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.