Vault 2.x release notes

Release notes provide an at-a-glance summary of key updates.

We encourage you to upgrade to the latest release of Vault to take advantage of continuing improvements, critical fixes, and new features.

Summary

Vault 2.x.x:

• Provides native AI agent support that improves security for the stochastic behaviors of AI agents and agent workflows, reduces manual setup costs, and reduces operational friction for teams that manage identity, secrets, and encryption across large environments.

• Connects to existing identity systems, delivers workload identity in SPIFFE-based environments, and syncs secrets to external platforms without depending on long-lived cloud credentials.

• Helps teams manage distributed infrastructure with less custom glue code and fewer one-off workflows. Operators can standardize credential rotation, support multi-region key management, automate Linux local account management, and use more guided UI workflows when they onboard teams, create policies, and discover Vault capabilities.

Vault 2.2.0

Released: 2026-10-15

New features

Enterprise

• OAuth2 access tokens for Azure static roles: The Azure secrets engine can now generate OAuth2 access tokens directly for static roles. Platform teams can grant token access separately from credential access, and application developers can receive ready-to-use tokens without ever seeing the underlying client secret.

• LDAP secrets engine improvements

  Enterprise
  :
  • Account unlocking for root-managed static roles: The LDAP secrets engine can clear login-failure lockouts for Active Directory accounts associated with root-managed static roles.
  • Rotate on read: You can rotate credentials on read for infrequently used LDAP static roles.
  • Health checks: You can validate LDAP secrets engine connectivity, authentication, and managed account status with scheduled monitoring and recovery workflows for locked accounts.

• Secrets Sync improvements

  Enterprise
  :
  • Database secrets: Secrets Sync pushes static and rotating database secrets to sync destinations. Vault pushes updates when database secrets change to keep destinations aligned with Vault.
  • Target-side encryption: You can configure encryption at rest for secrets pushed to AWS Secrets Manager and Google Cloud Secret Manager using cloud service provider-managed encryption keys.
  • Multi-region destinations: You can push secrets to multiple AWS Secrets Manager and Google Cloud Secret Manager regions.

• Vault Client

  Enterprise
  : Vault Client now available in public beta. The client binary includes Vault Agent, Vault Proxy, and a limited set of Vault CLI commands without the full Vault server binary.

• Vault ServiceNow credential resolver: The Vault ServiceNow credential resolver adds discovery support for bearer tokens, SSH credentials, and SNMPv3 devices.

• Enhanced Vault GUI dashboard with improved content organization and guidance:

  • Feature spotlight
    Enterprise
    : Highlights additional features and guides you through key improvements after an upgrade.
  • Submit feedback button
    Enterprise
    : You can submit feedback directly from the Vault GUI.
  • Upgrade analyzer
    Enterprise
    : Provides tailored recommendations, prerequisites, known issues, and feature highlights for specific upgrade paths.
  • Secrets engine catalog revamp: Adds secrets engine descriptions and predefined tags. You can sort, search, and filter the catalog to find an engine that supports static, rotating, or dynamic secrets.
  • Terraform code generator (phase 2)
    Enterprise
    : Configuration forms and wizards provide Terraform Vault provider code snippets, a CLI command, and an option to apply the change all from the Vault GUI.
  • List standardization (phase 1): Standardizes list views for entities, secrets engines, policies, groups, and namespaces.
  • Collapsible sidebar: You can collapse and expand the sidebar.
  • View secrets in YAML format: You can view KV v1 and KV v2 secrets in YAML format with secret values hidden by default.

• SCIM identity provisioning

  Enterprise
  : System for Cross-domain Identity Management (SCIM) provisioning is generally available. You can automatically provision users and groups from your identity provider or identity governance tool into Vault.

• Sentinel 0.41.0 update

  Enterprise
  : Sentinel adds s390x architecture support for builds, tests, and Docker images.

• GUI analytics: You can opt in to GUI analytics to share feature usage patterns with the Vault product team.

• AWS IAM roles for service accounts snapshots: You can authenticate and automate snapshots using AWS Identity and Access Management (IAM) roles for service accounts.

• TPM auth method

  Enterprise
  : You can authenticate Linux workloads using Trusted Platform Module (TPM)-backed identity, reducing reliance on pre-shared bootstrap credentials and limiting credential replay across hosts.

• Post-quantum cryptography support in PKI: The PKI secrets engine supports Module-Lattice-Based Digital Signature Algorithm (ML-DSA) X.509 certificates.

• Crypto agility in the Transit secrets engine

  Enterprise
  : You can update the cryptographic algorithm for a key without changing the key configuration in downstream systems.

• FF1 support in Transform secrets engine

  Enterprise
  : The Transform secrets engine supports the FF1 algorithm and a rewrap endpoint for format-preserving encryption.

• Azure secrets engine two-credential rotation: Seamless rotation stages the next credential for a static role before the current credential expires. Seamless rotation reduces availability risks caused by the eventual consistency functionality in Azure.

• PKI certificate key export and import: Use operator-controlled export key pairs to export a certificate authority private key from one Vault PKI mount and import it into another with RSA-OAEP or ECDH-ES wrapping.

Bug fixes and security patches

• OAuth resource server
  Enterprise
  : Vault rejects entity alias creation when an explicit mount_accessor names an OAuth resource server profile whose issuer differs from the issuer in the same request. Vault previously stored the alias, which then bound the issuer it named rather than the profile the accessor pointed at. Aliases already stored with that mismatch keep working, and updates through identity/entity-alias/id/{id} are unaffected.

Improvements and behavior changes

• KV v2 snapshot recovery: You can now read and recover KV v2 secrets from a loaded cluster snapshot, including in-place recovery and copy-from-path within the same mount and namespace. Refer to the Recover a secret from a snapshot guide for more details.

• Role-level password policy assignment for AD/LDAP: You can assign password policies to Active Directory and LDAP roles.

• EdDSA support for OAuth resource server profiles

  Enterprise
  : OAuth resource server profiles now accept EdDSA in supported_algorithms and validate JWTs signed with Ed25519 keys. Vault reads Ed25519 keys from PEM-encoded static keys or from a JWKS endpoint. Refer to Supported algorithms for more details.

• OAuth resource server

  Enterprise
  :
  • Writes to sys/config/oauth-resource-server/{name} return 200 OK with the stored profile instead of 204 No Content with an empty body. Vault returns validation warnings alongside the profile data rather than in place of it.
  • Read and write responses include a mount_accessor field holding the assembled synthetic accessor (oauth-resource-server_<namespace_id>_<config_id>), so you no longer need to build the accessor by hand to create an entity alias.
  • Listing profiles returns a key_info map keyed by profile name, with the config_id and mount_accessor of each profile. Vault sorts the profile names, and warns when it lists a profile whose details it cannot read.
  • You can bind an entity alias to a profile by setting profile_name or config_id together with external_id. Vault resolves the profile in the request namespace and derives both the mount accessor and the issuer from it, so binding an alias no longer requires the accessor or the issuer URL. The two fields are mutually exclusive with each other and with mount_accessor, and apply only when you create an alias.

• Vault server TLS certificate polling: Vault server nodes can periodically check for updated TLS certificates and reload them without downtime.

• Terraform secrets engine root token rotation: You can rotate the root token for the Terraform secrets engine.

• Vault Secrets Operator instant updates: Vault Secrets Operator (VSO) v1.6 immediately delivers updates for dynamic, auto-rotating, and manually rotated database, KV, Azure, and LDAP secrets.

Vault 2.1.2

Released: 2026-10-07

New features

• None.

Bug fixes and security patches

• Fixed: PKI ACME issues certificate With unvalidated SANs
• Fixed: Vulnerability to arbitrary code execution via plugin catalog entries restored from raft snapshots
• Fixed: ACL policy cache vulnerable to cross-namespace policy resolution
• Fixed: Inconsistent ACL policy evaluation may allow bypass of deny restrictions

Improvements and behavior changes

• None.

Vault 2.1.1

Released: 2026-09-16

New features

• None.

Bug fixes and security patches

• Secrets sync
  Enterprise
  : Fixed the total secrets count on the secrets sync overview page, which was bound to the wrong key in the API response and displayed an incorrect total.
• Login page: Fixed a flickering issue on the login page that occurred when a trailing slash was present in the namespace field.
• Vault Agent registry
  Enterprise
  : Fixed ceiling policies not displaying on the Vault Agent registry page due to an incorrect property name.
• Leases: Pagination controls now render regardless of whether a filter/search term is applied to the leases list.
• Dependency update: Vulnerability patch for dompurify.

Improvements and behavior changes

• Secrets import

  Enterprise
  : AWS Secrets Manager and Azure Key Vault import sources support allowed_ipv4_cidrs to allow trusted private endpoints while blocking other RFC 1918 private addresses by default.

• JWT/OIDC Auth Plugin: Added a new Okta provider that fetches groups from the Okta Admin API when fetch_groups=true and Vault detects group truncation.

• PKI secrets engine: Added extra_names_from_csr to PKI roles. When set to a list of dotted-decimal OIDs, Vault passes matching non-standard Subject attributes from a caller-supplied CSR through to the issued certificate instead of silently discarding them. Effective on /sign and enrollment protocols (CMPv2, SCEP, EST); silently ignored on /issue.

Vault 2.1.0

Released: 2026-09-01

New features

Enterprise

• Native support for securing agentic workflows: Out of beta and Generally Available. The Agentic IAM no longer requires an activation flag to use.

Bug fixes and security patches

Enterprise

• OAuth resource server: Vault treats an empty authorization_details array in Rich Authorization Requests the same as an omitted array.

• OAuth resource server: Vault now correctly normalizes issuers before looking up the OAuth resource server profile during alias creation.

Improvements and behavior changes

Enterprise

• Agent registry: Ceiling policies can now include policies containing deny statements without requests for those registered agents failing.

• OAuth resource server:

  • Revocation of OAuth 2.0 JWTs now available using token revoke APIs. Note that, as JWTs are immutable, revocation prevents them from being used with Vault, even if you continue to use them elsewhere.
  • You no longer need an activation flag to use the OAuth resource server API.
  • issuer_id is now immutable once you create a profile and cannot be modified during profile updates.
  • Vault now supports templated paths in Rich Authorization Requests.
  • Vault now supports allowed, denied, and required parameters in Rich Authorization Requests.
  • To increase compatibility, you can now modify JWT uniqueness claims to be non-standard and use Vault with IdPs that do not comply to the standard.

Vault 2.0.4

Released: 2026-08-04

Bug fixes and security patches

• Fix: Fixed key_info output when querying the list of agent registrations by name with the API endpoint /agent-registry/registration/display-name.
• SCIM guardrails
  Enterprise
  : Manual entity merges now respect SCIM ownership rules and can no longer use the identity merge API to bypass SCIM-managed resource boundaries.

Improvements and behavior changes

• Agent registry: Added the entity_id field to key_info in the output of /agent-registry/registration/id and /agent-registry/registration/display-name.
• SCIM filtering
  Enterprise
  : The SCIM /Users and /Groups list endpoints now support limited filtering for reconciliation and delta-sync workflows.
• SCIM User.groups
  Enterprise
  : SCIM user responses now include the read-only groups field for direct memberships in groups that the same SCIM client manages.
• License Utilization Metrics:
  • High watermark tracking of service account library sets managed by LDAP and OpenLDAP secrets engines:
    • ldap_library_max_set_count.current_month_estimate
    • ldap_library_max_set_count.previous_month_complete
    • openldap_library_max_set_count.current_month_estimate
    • openldap_library_max_set_count.previous_month_complete
• Product Usage Metrics:
  • Added a count of service account library sets managed by LDAP and OpenLDAP secrets engine mounts across all namespaces:
    • vault.secret.engine.ldap.library.set.count
    • vault.secret.engine.openldap.library.set.count

Vault 2.0.3

Released: 2026-06-17

New features

Enterprise

• Native support for AI agents: Available to all customers in public beta.

Bug fixes and security patches

• Fix: Fixed stuck dropdowns in the Transit secrets engine Vault GUI.

Improvements and behavior changes

• Azure secrets engine: Improved reliability for dynamic roles using ephemeral service principals: Vault now uses a single Microsoft Graph API request to create the application and its initial client secret, significantly reducing Azure eventual consistency delays that could cause newly generated secrets to be temporarily rejected as invalid.
• Cloud Foundry auth plugin:
  • Lazy CF client initialization: The CF auth plugin no longer calls the CF API during plugin initialization. Vault now creates the CF client lazily and only when a configuration write or login request requires it.
  • force_new_client flag: Added a new force_new_client configuration flag. When enabled, the plugin creates a new CF client for every login request instead of using the shared cached client.
• Charts: Migrated charts from Lineal to Carbon Charts in the Client usage overview and Vault usage dashboards for a more polished and consistent visual experience.
• Donut chart tooltips: Refined tooltip styling and functionality on donut charts for better clarity and consistency.
• ember-basic-dropdown: Bumped to ~8.9.0 to satisfy a peer dependency requirement with @hashicorp/design-system-components.
• Babel preset: Reinstalled @babel/preset-env at ~7.29.5 to stay current with the JavaScript build ecosystem.
• Dependency overrides: Removed stale dependency overrides from ui/package.json to reduce unnecessary version constraints.

Vault 2.0.2

Released: 2026-06-04

Bug fixes and security patches

• Fix: Local account update failure. Vault failed to complete account rotation with the error: Error writing data to <path>: context deadline exceeded.

• Fix: Enterprise Azure Secrets Engine credential failure. Vault intermittently failed during credential creation with the error: Resource does not exisit.

• Go update: Vulerability patch for golang.org/x/crypto.

• Go update: Vulerability patch for golang.org/x/net.

Improvements and behavior changes

• Removed the IPC_LOCK capability for official OCI container images while preserving the non-root vault user runtime model.

Vault 2.0.1

Released: 2026-05-19

Bug fixes and security patches

• Fix: MSSQL database secrets engine bug. Fixed lease revocation to work without sysadmin privileges by replacing the undocumented sp_msloginmappings procedure with a metadata query. The plugin now functions with VIEW ANY DEFINITION and VIEW SERVER STATE permissions instead of requiring full sysadmin access.

Improvements and behavior changes

• License utilization dashboard: New UI dashboard for /sys/billing/overview data.

• /sys/billing/overview: Now retains 37 months of usage data and adds start_month and end_month query parameters.

• License utilization metrics: Added census and billing metrics.

  • GCP KMS operation counts for data protection API calls: gcp_kms_operation_count.current_month_estimate and gcp_kms_operation_count.previous_month_complete
  • OIDC token units for duration-adjusted OIDC token issuance: normalized_oidc_tokens_issued.current_month_estimate and normalized_oidc_tokens_issued.previous_month_complete
  • SPIFFE JWT token units for duration-adjusted SPIFFE JWT token issuance: normalized_spiffe_jwt_token_units.current_month_estimate and normalized_spiffe_jwt_token_units.previous_month_complete
  • High watermark tracking of local account static roles managed by OS secrets engine: os_local_static_max_role_count.current_month_estimate and os_local_static_max_role_count.previous_month_complete
  • PKI External CA certificate units for duration-adjusted PKI External CA certificate issuance: normalized_external_ca_cert_units.current_month_estimate and normalized_external_ca_cert_units.previous_month_complete

• Product usage metrics:

  • Added a count of local account static roles managed by mounts of OS secrets engine across all namespaces (secret.engine.os.local.account.static.role.count).
  • Added a count of agent registrations across all namespaces (vault.agentregistry.agent.registrations.count).
  • Added a count of agent registrations with RAR toggled off across all namespaces (vault.agentregistry.agent.registrations.with_rar_off.count).
  • Added a count of agent registrations with RAR toggled on across all namespaces (vault.agentregistry.agent.registrations.with_rar_on.count).
  • Added a count of OAuth resource server configurations across all namespaces (vault.oauth.resource.server.config.count).
  • Added a count of OAuth resource server configurations with RAR toggled on across all namespaces (vault.oauth.resource.server.config.with_rar_on.count).
  • Added a count of OAuth resource server configurations with RAR toggled off across all namespaces (vault.oauth.resource.server.config.with_rar_off.count).

• JWT/OIDC auth plugin - Added multi-JWKS key ID cache: JWT authentication with multiple JWKS URLs (jwks_pairs) now uses a key ID cache so Vault skips unnecessary JWKS endpoint refreshes during login. The plugin first checks all in-memory caches for the token's key ID before making any network calls. Remote JWKS endpoints are only re-fetched when no cache contains the key ID, such as after a key rotation.

• Wildcards and globs no longer permitted in templated policy paths: Vault now returns a "permission denied" error if you include wildcards and globs in the rendered output for identity templates. Refer to the Important changes entry for more details.

Vault 2.0.0

Released: 2026-04-14

New features

Enterprise

• SCIM identity provisioning - Automate identity lifecycle management by provisioning entities and groups in Vault from external identity platforms.
• SPIFFE JWT-SVID support - Let authenticated workloads request JWT-SVIDs from Vault so they can participate in SPIFFE-based identity workflows.
• Visual policy generator - Create policies faster and reduce manual policy authoring by generating ACL policy snippets from the Vault GUI.
• Feature introduction pages - The Vault GUI now provides guided overviews for key Vault capabilities that help you understand core features without leaving the GUI.
• Namespace onboarding workflow - Answer a few key questions in the Vault GUI to create new namespaces then continue in the GUI, CLI, or Terraform.
• Secret Sync - Use workload identity federation (WIF) to sync secrets to external systems without storing static credentials.
• Envelope encryption - Use Transit for in-place encryption workflows where Vault protects data encryption keys and your applications encrypt and decrypt local data.
• Public CA integration - Use Vault to interface to public CAs in order to issue certificates.
• AWS KMS multi-region keys - Create and replicate managed keys across AWS regions so you can support multi-region encryption and disaster recovery workflows.
• Local accounts secrets engine - Use Vault to automatically rotate Linux local account credentials.
• LDAP static role rotation enhancements - Manage LDAP static credentials with more flexibility by adding initial passwords, self-managed rotation, schedules, and retry controls.
• Rotation policies - Standardize how Vault handles failed automated rotations by defining reusable retry behavior for supported roles.

Bug fixes and security patches

• Fix: Credential rotation bug. Vault Agent backoff reduces aggressive retries during secret rotation so that agents create less unnecessary network traffic and server load.
• Fix: Repaired the integrity of duplicate and/or dangling entity aliases.

Improvements and behavior changes

• The Vault UI navigation now organizes features around common operator tasks so users can find related capabilities faster.
• In-product feature descriptions explain what features do and when to use them so that users can evaluate capabilities in context.
• Azure secrets engine adds role metadata support, separates static credential import, and lowers the minimum TTL for static roles to 30 days so operators can manage Azure roles with more consistency.
• Event notifications support subscriptions from secondary clusters for events on the primary cluster so multi-cluster deployments can react with lower latency.
• External plugin management is easier in the Vault GUI so operators can manage external versions of built-in plugins without relying only on the API or CLI.
• IBM Passport Advantage Online license support lets Vault Enterprise use IBM Passport Advantage Online license keys so customers can reduce licensing fulfillment delays.
• Support for an additional licensing framework aligns pricing with workload, automation, and machine identity growth so billing better reflects platform usage.
• JWT auth updates improve JWT-based authentication workflows.
• KMIP Bring Your Own CA: Use the import endpoint to manage multiple CAs for client verification and make it possible to import external CAs.
• Azure OIDC Provider supports fetching groups from the Azure Graph API.
• Rotation retries use exponential backoff and orphan handling so Vault can retry failed root and static credential rotations without overloading the system. Vault 2.0.0 supports LDAP static roles in addition to the engines that already support root rotation.
• TCP listener: Added the max_token_header_size option to limit the size of authentication token header values passed with X-Vault-Token or Authorization: Bearer. The default limit is 8 KB (8192 bytes), which covers all current opaque Vault tokens. Operators who use enterprise JWT tokens or OIDC tokens with large authorization_details claims should evaluate their token sizes and raise the limit proactively. See the TCP listener configuration for configuration details and upgrade guidance.

Feature deprecations and EOL

Please refer to the deprecation notices for up-to-date information on feature deprecations and plans.