HashiCorp Vault Updates Block Snapshot-Restored Plugin Code Execution

P2 — VALIDATE AND UPDATENot provided by the authority · Not provided by the authorityEXPLOITATION: NOT STATED

Quick Answer

HashiCorp published HCSEC-2026-41 for Vault Community Edition and Vault Enterprise through 2.1.1 using Shamir seals with an external plugin directory. Inventory the exact affected scope, apply Vault Community Edition 2.1.2; Vault Enterprise 2.1.2, 1.21.12, 1.20.17, or 1.19.23 on every node and Enterprise secondary, validate dependent operations, and preserve change evidence.

Validate Vault Scope And Apply The Supported Fix

What to do now: Inventory Vault Community Edition and Vault Enterprise through 2.1.1 using Shamir seals with an external plugin directory, match versions and enabled features to the authority's scope, apply supported remediation, validate representative operations, and document exceptions.

Open the authoritative advisory

Last verified: 2026-10-08 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeVault Community Edition and Vault Enterprise through 2.1.1 using Shamir seals with an external plugin directory
AdvisoryHCSEC-2026-41
CVECVE-2026-105816
Authoritative release date2026-10-07 21:34:25.206 UTC
Authority revision date2026-10-07 21:34:25.206 UTC
Affected versionsClusters using Shamir seals, an external plugin directory, and privileged Integrated Storage snapshot restoration; auto-unseal clusters or clusters without a plugin directory are not affected.
Fixed versionVault Community Edition 2.1.2; Vault Enterprise 2.1.2, 1.21.12, 1.20.17, or 1.19.23 on every node and Enterprise secondary
CVSS base scoreNot provided by the authority
CVSS severityNot provided by the authority
Exploitation statusNot stated by the authority; no exploitation claim is inferred.

What Changed

A privileged operator restoring a crafted Raft snapshot could introduce plugin catalog entries that execute a binary outside the configured plugin directory.

What To Validate Now

  1. Inventory. Locate Vault Community Edition and Vault Enterprise through 2.1.1 using Shamir seals with an external plugin directory; record versions, enabled features, exposure paths, owners, dependencies, support channels, and maintenance groups.
  2. Establish applicability. Compare every deployment with the authority's affected statement: Clusters using Shamir seals, an external plugin directory, and privileged Integrated Storage snapshot restoration; auto-unseal clusters or clusters without a plugin directory are not affected. Do not infer applicability from product family, CVSS, or Internet reachability alone.
  3. Remediate. Apply Vault Community Edition 2.1.2; Vault Enterprise 2.1.2, 1.21.12, 1.20.17, or 1.19.23 on every node and Enterprise secondary through the authority-supported channel and follow the current advisory.
  4. Validate. Confirm the resulting Vault build or managed state, exercise representative services and recovery paths, monitor for regressions, and retain the result.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Upgrade every active, standby, performance-secondary, and disaster-recovery node. Review restored snapshots and re-register any rejected plugin with its binary inside the configured directory. Preserve pre-change state, installation output, logs, validation evidence, and rollback decisions.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.