Hashicorp Release Notes
35 release notes curated from 2 sources by the Releasebot Team. Last updated: Nov 13, 2026
Hashicorp Products
- Nov 12, 2026
- Date parsed from source:Nov 12, 2026
- First seen by Releasebot:Nov 13, 2026
v2.2.2
Vault releases security and reliability improvements, including case-insensitive enforcement of explicit deny rules, safer audit logging, and fixes across authentication, secrets, PKI, and the UI. It also updates plugins and adds TPM auto-auth support to Vault Proxy.
November 12, 2026
SECURITY
- core/acl: Harden explicit deny rule evaluation by matching requested paths case-insensitively.
CHANGES
- auth/alicloud: Update plugin to v0.24.1
- auth/cf: Update plugin to v0.24.1
- auth/jwt: Update plugin to v0.27.2
- auth/kerberos: Update plugin to v0.18.1
- auth/oci: Update plugin to v0.22.1
- core: Bump Go version to 1.27.4
- core/acl: Fix an issue where explicit deny policy rules were not enforced against case variants of the denied path. Explicit deny rules now also match the requested path case-insensitively, subject to the usual rule specificity. For example, a deny on secret/data/example now also denies requests to secret/data/EXAMPLE.
- database/couchbase: Update plugin to v0.17.1
- database/elasticsearch: Update plugin to v0.21.1
- database/mongodbatlas: Update plugin to v0.18.1
- database/redis: Update plugin to v0.9.1
- database/snowflake: Update plugin to v0.17.1
- proxy/agent: Custom plugins or integrations that return interactive HTML through Agent or Proxy will no longer render interactively in a browser.
- secrets/alicloud: Update plugin to v0.23.1
- secrets/azure: Update plugin to v0.28.5+ent
- secrets/keymgmt: Update plugin to v0.20.2+ent
- secrets/mongodbatlas: Update plugin to v0.18.1
- secrets/terraform: Update plugin to v0.15.1
IMPROVEMENTS
- core: Include the namespace ID in mount setup failure logs
- core: Update github.com/go-jose/go-jose/v4 to v4.1.6 and golang.org/x/net to v0.62.0
- ui: Show "Never" as the last Vault rotation on the LDAP role credentials page when a static role has not been rotated, instead of a date in year 0001.
BUG FIXES
- Transit (enterprise): Fix cache bug that led to non-zero auto_rotate_period values being written to the cache with managed keys
- agent/pki-external-ca (enterprise): Fix premature certificate reissuance on auto-auth re-authentication so certificate renewal respects percent_renew_before_expiry instead of being triggered by token updates.
- audit: Fixed a bug where Vault returned HTTP 500 when a large response (e.g. a PKI ?help=1 request) could not be written to a syslog audit device due to the OS Unix datagram socket size limit (EMSGSIZE / ENOBUFS). The syslog sink now splits oversized audit payloads into safe-sized chunks and retries transiently full socket buffers.
- audit: Fixes a panic that can occur when audit broker not initialized during teardown.
- auth/approle: Reject expired SecretIDs during login instead of relying on periodic tidy cleanup.
- auth/spiffe (enterprise): Fix an issue where renewable tokens were not being renewed
- core (enterprise): Fix a panic and partial namespace creation when the root agent-registry mount is unavailable
- core/census (enterprise): Fix the previous_month_complete census gauge reporting 0 in the first month after the billing start date auto-rolls, so the previous billing cycle's final client count is reported.
- core/plugin: Fix an issue where external secrets engine and auth plugins remained read-only after failing to load during startup or unseal. Operators can now restore the missing binary or registration and reload the plugin to resume writes without restarting Vault.
- core: Fix an issue where policy path matching could be inconsistent for requests that differ only by a trailing slash.
- identity: Use the reporting conflict resolver only while reloading in case-sensitive mode, to avoid collecting duplicates after unseal.
- pki-external-ca: Fix premature deletion of revoked certificate records during tidy; revoked orders are now retained until the certificate's NotAfter date rather than the ACME order expiry
- secrets/azure: Continue permanent application cleanup when the active application is already absent, allowing later cleanup attempts to retry the purge.
- secrets/azure: Retry transient Microsoft Graph 403/404 errors when adding newly created service principals to Azure groups.
- secrets/kv: Fixed an issue in KV v1 where writing a secret path containing consecutive slashes caused list operations to return "/" as a directory entry, producing an infinite loop in the Vault UI breadcrumb.
- tpm: tpm auth now respects the InsecureSkipVerify option
- ui: Fix the database overview page to list both dynamic and static roles and allow credential generation, and restore the Roles tab for users with only static-role permissions
- ui: fixes pagination on entities list table
- vault proxy: Support tpm method in the auto_auth block to match parity with agent.
- Nov 11, 2026
- Date parsed from source:Nov 11, 2026
- First seen by Releasebot:Nov 11, 2026
v1.17.2
Terraform 1.17.2 improves configuration generation performance for large HCP Terraform queries and fixes provider dependency cycles and repeated warnings.
1.17.2 (November 11, 2026)
ENHANCEMENTS:
- query: Improve performance and reduce allocations when generating configuration from large HCP Terraform queries. (#39470)
BUG FIXES:
- Providers referencing a managed resource with detroy=false can cause a cycle (#39507)
- init: Fix repeated unavailable-provider schema warnings in log output (#39517)
All of your release notes in one feed
Join Releasebot and get updates from Hashicorp and hundreds of other software products.
- Oct 28, 2026
- Date parsed from source:Oct 28, 2026
- First seen by Releasebot:Oct 29, 2026
v1.17.1
Terraform 1.17.1 fixes file preservation on formatting errors and improves policy evaluation and reporting during destroy plans and resource replacement.
1.17.1 (October 28, 2026)
BUG FIXES:
- fmt: The original content of a file is now preserved if Terraform experiences an error writing to the original file. (#39303)
- Always evaluate module policies during destroy plan (#39455)
- stacks: report every policy result for a replaced resource instead of only one of them (#39453)
- Oct 22, 2026
- Date parsed from source:Oct 22, 2026
- First seen by Releasebot:Oct 23, 2026
v1.16.7
Terraform fixes test-schema panics with deprecated values and updates Go certificate trust to reject certificates from compromised eMudhra intermediates.
1.16.7 (October 22, 2026)
BUG FIXES:
- command/test: Avoid panic when testing schema w/ deprecated values (#39406)
NOTES:
- Terraform is now built with Go 1.26.10, which no longer trusts certificates issued through a set of compromised eMudhra intermediate CAs (CVE-2026-111943) (#39417)
- Oct 15, 2026
- Date parsed from source:Oct 15, 2026
- First seen by Releasebot:Oct 16, 2026
v2.2.0
Vault releases a major update centered on AI agent security, with an Agent Registry and OAuth-based access, plus broad advances in PKI, identity, secrets management, and the UI. It also delivers extensive security hardening and breaking changes across authentication, policies, and containers.
October 15, 2026
Original source
BREAKING CHANGES:
containers: Remove cap_ipc_lock capability on vault at build time to allow running Vault in common container runtimes. Vault in containers will no longer be able to call mlock() to lock memory. Operators should set disable_mlock = true in Vault's configuration. Runtime operators are advised to disable swapping to guarantee data safety.
containers: The following packages have been removed from UBI based container images: gnupg, openssl, procps.
containers: set cap_ipc_lock capability on vault at build time. Container runtimes will need to add IPC_LOCK capabilities when running the vault container.
physical/postgresql: breaking change - PostgreSQL storage backend authentication now prefers Azure Workload Identity over Managed Identity. Update go-pgmultiauth to v1.1.0. Existing Managed Identity-based PostgreSQL configurations may stop working if Workload Identity is configured. Affected users must migrate PostgreSQL authentication to Workload Identity.
pki: ACME finalization with the default sign-verbatim directory policy now rejects CSRs that contain URI SANs, email SANs, or Other SANs. ACME challenges only verify DNS names and IP addresses; those SAN types are never validated and must not appear in issued certificates. Operators who require the previous behaviour can set default_directory_policy = "sign-verbatim-unsafe" in config/acme, accepting that the resulting certificates may contain unverified identity claims.
sdk/helpers/docker: Migrate docker helpers from github.com/docker/docker to github.com/moby/moby. This was necessary as github.com/docker/docker is no longer maintained. Resolves GHSA-x744-4wpc-v9h2 and GHSA-pxq6-2prw-chj9.
SECURITY:
Upgrade cloudflare/circl to v1.6.3 to resolve CVE-2026-1229
Upgrade filippo.io/edwards25519 to v1.1.1 to resolve GO-2026-4503
acl: Fix privilege-escalation vulnerability where a denied_parameters constraint on the policies request field could be bypassed by submitting a mixed-case policy name (e.g. "Super-Admin" instead of "super-admin"). Vault now normalizes the policies parameter to lowercase before evaluating allowed_parameters/denied_parameters constraints.
api/auth/gcp: Update go.opentelemetry.io/otel/sdk to fix CVE-2026-39883.
api/auth: Update github.com/go-jose/go-jose to fix security vulnerability CVE-2026-34986 and GHSA-78h2-9frx-2jm8.
api: Update golang.org/x/net to resolve GO-2026-4918
auth/aws: Fix an issue where a user may be able to bypass authentication to Vault due to incorrect caching of the AWS client
auth/cert: Ensure that the certificate being renewed matches the certificate attached to the session.
auth/radius: Added case_insensitive_names toggle to prevent username collisions and enable case-insensitive user handling.
core (enterprise): Prevent policy-name canonicalization bypasses in ACL parameter restrictions.
core/acl: Fix LIST ACL bypass where a trailing-slash request could skip a more-specific deny rule.
core/identity: Reject wildcards in rendered identity templates.
core/plugin: Fix plugin catalog entries restored from a raft snapshot, written through sys/raw, or replicated being able to run a binary outside plugin_directory.
core/policy: Harden request-time ACL construction to ignore malformed legacy policy references containing path-navigation segments (. or ..) so traversal-style names are never resolved or applied.
core: Correctly remove any Vault tokens from the Authorization header when this header is forwarded to plugin backends. The header will only be forwarded if "Authorization" is explicitly included in the list of passthrough request headers.
core: Fixed a bypass of exact-deny ACL policies where case-variant AppRole, AWS, Azure, GCP, Kubernetes, SCEP, or TPM role names, GitHub team or user policy mapping keys, certificate or CRL names, ACL/RGP/EGP policy names, or userpass usernames could evade the deny and be resolved by the backend to the same protected resource. Okta group names, LDAP and RADIUS names on mounts left in their default case-insensitive configuration, and Enterprise SCIM client names (identity/scim/client/<name>, where a case-variant write overwrites the existing client) are not covered by this fix and remain subject to the same bypass; avoid combining a wildcard allow with an exact deny on those mounts and paths.
core: Resolve GHSA-j88v-2chj-qfwx by removing our dependency on github.com/jackc/pgx/v3 and github.com/jackc/pgx/v4
core: Resolve GO-2026-4518 and GHSA-jqcq-xjh3-6g23 by upgrading to github.com/jackc/pgx/v5
core: Update github.com/Azure/go-ntlmssp to fix security vulnerability v0.1.1.
core: Update github.com/apache/thrift to fix security vulnerability GHSA-wf45-q9ch-q8gh
core: Update github.com/apache/thrift to v0.24.0 to fix security vulnerability GHSA-8wv5-x4w7-5gww.
core: Update github.com/aws/aws-sdk-go-v2/ to fix security vulnerability GHSA-xmrv-pmrh-hhx2.
core: Update github.com/go-jose/go-jose to fix security vulnerability CVE-2026-34986 and GHSA-78h2-9frx-2jm8.
core: Update github.com/hashicorp/go-getter to fix security vulnerability GHSA-92mm-2pjq-r785.
core: Update github.com/jackc/pgx/v5 to fix security vulnerability GHSA-j88v-2chj-qfwx.
core: Update go.etcd.io/etcd/client/pkg/v3 to v3.7.1 to fix security vulnerability GO-2026-6107.
core: Update go.opentelemetry.io/otel/sdk to fix CVE-2026-39883.
core: Update golang.org/x/crypto to v0.56.0 to fix security vulnerabilities GO-2026-6354 and GO-2026-6355.
core: Update golang.org/x/net to resolve GO-2026-4918"
core: Update google.golang.org/grpc to v1.83.2 to fix security vulnerability GHSA-2v4p-qf9q-27wj.
core: Update software.sslmate.com/src/go-pkcs12 to v0.7.2 to fix security vulnerability GO-2026-5052.
core: Use constant-time recovery token comparison.
core: Validate both path and file_path cannot be empty for requests to sys/audit/{path}
core: Reject URL-encoded paths that do not specify a canonical path.
http: Add configurable max_token_header_size listener option (default 8 KB) to bound the size of authentication token headers (X-Vault-Token and Authorization: Bearer), preventing a potential denial-of-service attack via oversized header contents. The stdlib-level MaxHeaderBytes backstop is also now set on the HTTP server. Set max_token_header_size = -1 to disable the limit.
identity/scim (enterprise): The identity/entity/merge endpoint now rejects requests that involve any SCIM-managed entity, preventing privileged operators from bypassing SCIM ownership guardrails to transfer aliases, group memberships, or policies across SCIM boundaries.
identity: Prevent the entity batch-delete endpoint (identity/entity/batch-delete) from deleting the underlying storage of entities that belong to another namespace.
identity: Entity name updates now reject mismatched id or external_id selectors to prevent retargeting updates to a different entity.
sdk: Resolve GHSA-j88v-2chj-qfwx by removing our dependency on github.com/jackc/pgx/v3 and github.com/jackc/pgx/v4
sdk: Resolve GO-2026-4518 and GHSA-jqcq-xjh3-6g23 by upgrading to github.com/jackc/pgx/v5
sdk: Update github.com/Azure/go-ntlmssp to fix security vulnerability v0.1.1.
sdk: Update github.com/go-jose/go-jose to fix security vulnerability CVE-2026-34986 and GHSA-78h2-9frx-2jm8.
sdk: Update github.com/jackc/pgx/v5 to fix security vulnerability GHSA-j88v-2chj-qfwx.
sdk: Update golang.org/x/net to resolve GO-2026-4918"
secrets/spiffe (enterprise): Ensure template values are properly escaped.
transform (enterprise): Add appropriate db specific quoting and escaping.
ui: Upgrade dompurify to 3.4.0
ui: Disable scarf analytics for ui builds.
vault/sdk: Upgrade cloudflare/circl to v1.6.3 to resolve CVE-2026-1229
vault/sdk: Upgrade go.opentelemetry.io/otel/sdk to v1.40.0 to resolve GO-2026-4394
CHANGES:
License: Add Agentic IAM terms to client licensing model and update terms for Vault Platform licensing model.
api: Removed the hcp_link_status and hcp_link_resource_ID fields from the sys/seal-status response.
audit: A new top-level key called supplemental_audit_data can now appear within audit entries of type "response" within the request and response data structures. These new fields can contain data that further describe the request/response data and are mainly used for non-JSON based requests and responses to help auditing. The audit-non-hmac-request-keys and audit-non-hmac-response-keys apply to keys within supplemental_audit_data to remove the HMAC of the field values if so desired.
auth/alicloud: Update plugin to v0.24.0
auth/azure: Update plugin to v0.25.1
auth/cf: Update plugin to v0.24.0
auth/gcp: Update plugin to v0.24.1
auth/jwt: Update plugin to v0.27.1
auth/kerberos: Update plugin to v0.18.0
auth/kubernetes: Update plugin to v0.25.0
auth/oci: Update plugin to v0.22.0
auth/saml: Update plugin to v0.9.0
auth/token: JWT revocation via auth/token/revoke-self and auth/token/revoke-accessor is no longer supported. auth/token/revoke and auth/token/revoke-orphan now require the full JWT to revoke an OAuth JWT and reject the internal stored JWT ID form. Non-JWT Vault token behavior is unchanged.
cli: vault operator diagnose no longer runs an HCP Link connectivity check, and vault status no longer shows HCP Link status.
cli/status: vault status no longer forces the root namespace when querying seal status. It now respects the namespace set via VAULT_NAMESPACE or the -namespace flag, consistent with other CLI commands.
core/acl: LIST requests with a trailing slash now correctly respect more-specific deny policies. Previously, a deny on path "kv/" { deny } could be bypassed for LIST kv/private/ if a broader allow path "kv/" also existed. Policies relying on the previous (incorrect) behavior may now be denied.
core/managed-keys (enterprise): The response to API endpoint GET sys/managed-keys/:type/:name now
returns an array of string values for key usages, rather than an array of integer values. The strings used are 'encrypt' (1), 'decrypt' (2), 'sign' (3), 'verify' (4), 'wrap' (5), 'unwrap' (6), 'generate_random' (7), and 'mac' (8).
core/oauth-resource-server (enterprise): The write response for sys/config/oauth-resource-server/:name now returns HTTP 200 with the full profile object instead of HTTP 204 with an empty body. Validation warnings are returned alongside the profile data rather than in place of it.
core/plugin: Plugin catalog entries are now checked against plugin_directory whenever they are used, not only at registration. An entry whose command resolves outside the directory, including through a symlink, is refused with plugin command is outside of configured plugin directory, and mounts that use it are skipped at startup while keeping their data. Such plugins must be registered again with their binary inside plugin_directory.
core/policy: Vault now validates policy names with segment-aware checks. Empty names and names containing . or .. path segments are rejected for new policy writes and assignments, while names containing / and \ remain supported. During request-time ACL construction, legacy traversal-style policy references are not applied (treated as invalid and unresolved), which can reduce effective token permissions. Operators should audit and rename affected policies before upgrading.
core/raft: Limited concurrent retry-join workers to 20. Any further retry-join attempts while 20 are in progress will result in an error (too many concurrent raft retry joins in progress).
core: ACL and Sentinel EGP rule paths targeting a specific AppRole, AWS, Azure, GCP, Kubernetes, SCEP, or TPM role, GitHub team or user policy mapping key, certificate or CRL name, ACL/RGP/EGP policy name, or userpass username are now matched against the lowercased resource name, since these backends resolve those names case-insensitively. A rule written with a mixed-case resource name (for example auth/approle/role/MyRole) no longer matches requests for that resource and must be rewritten using the lowercase name (auth/approle/role/myrole). The lowercased form is also what Sentinel RGP and EGP policies observe as request.path, so policy rules that compare that value against a mixed-case path (for example request.path is "auth/approle/role/MyRole") must be updated as well. External auth and secret plugins are not affected by this normalization and continue to receive requests with their original casing. Existing deny rules using mixed-case resource names will fail open (become allow-all) after upgrade until rewritten with lowercase names.
core: Bump Go version to 1.27.1.
core: Require sudo capability for sys/mounts/auth/<path>/tune, matching sys/auth/<path>/tune.
core: Vault now rejects paths that are not canonical, such as paths containing double slashes (path//to/resource)
core: Vault will now redirect non-canonicalized paths (containing /./, /../, or //) to a cleaned path, instead of rejecting these requests
core: bump github.com/hashicorp/cap to v0.12.0
core: remove support for duplicate attributes in HCL configuration files and policy definitions. Parsing HCL with duplicate attributes now always fails, and the VAULT_ALLOW_PENDING_REMOVAL_DUPLICATE_HCL_ATTRIBUTES environment variable that previously restored the legacy behavior has been removed.
core: secondary DR requests can now be authenticated using a root token generated on the primary.
core: sys/generate-root and sys/replication/dr/secondary/generate-operation-token endpoints are now authenticated by default, with the old unauthenticated behaviour enabled by setting the new HCL config key enable_unauthenticated_access to include the value "generate-root" or "generate-operation-token" respectively.
core: sys/rekey endpoints are now authenticated by default, with the old unauthenticated behaviour enabled by setting the new HCL config key enable_unauthenticated_access to include the value "rekey".
core: Removed support for HCP Link, which connected self-managed Vault clusters to the HashiCorp Cloud Platform (HCP). Vault no longer starts an HCP Link connection, and the cloud stanza in the server configuration no longer has any effect and will be unrecognized.
database/couchbase: Update plugin to v0.17.0
database/elasticsearch: Update plugin to v0.21.0
database/mongodbatlas: Update plugin to v0.18.0
database/redis-elasticache: Update plugin to v0.9.1
database/redis: Update plugin to v0.9.0
database/snowflake: Update plugin to v0.17.0
http: Return 431 status code instead of 400 when token header size validation fails.
identity/scim (enterprise): Added "allow_group_adoption" toggle to allow or forbid a SCIM client from adopting groups.
identity/scim (enterprise): Added a check for case-duplicate identity resources which, if detected, will cause the SCIM operation to fail with an error message. To deduplicate identities, please use the force-identity-deduplication activation flag.
identity/scim (enterprise): Loading SCIM clients will now test for and remove duplicate client names. SCIM clients are now properly case insensitive.
identity/scim: Remove the SCIM activation flag; SCIM v2 endpoints are now always available without prior activation
identity: Require sudo capability to invoke the identity entity merge API endpoint (identity/entity/merge).
license utilization reporting (enterprise): Manual reporting bundles generated by vault operator utilization have a changed format. Notably they contain an array of snapshot_records instead of snapshots. The decoded_snapshot field in each record contains the human-readable data that was previously in the snapshots array.
mfa/duo: Upgrade duo_api_golang client to 0.2.0 to include the new Duo certificate authorities
oauth-resource-server: Prevent issuer_id from being mutated after OAuth Resource Server profile creation. Operators must delete and recreate profiles to change the issuer_id.
oauth-resource-server: Prevent unique_id_claim from being mutated after OAuth Resource Server profile creation. Operators must delete and recreate profiles to change the unique_id_claim.
oauth-resource-server: The OAuth Resource Server feature no longer requires activation via the sys/activation-flags/oauth-resource-server/activate endpoint.
oauth-resource-server: Update OAuth Resource Server config to include custom claim options for the token's unique identifier and actor.
packaging: Container images are now exported using a compressed OCI image layout.
packaging: UBI container images are now built on the UBI 10 minimal image.
secrets/ad: Update plugin to v0.23.0
secrets/alicloud: Update plugin to v0.23.0
secrets/azure: Update azure enterprise secrets plugin to include static roles.
secrets/azure: Update plugin to v0.28.3+ent
secrets/gcp: Update plugin to v0.25.0
secrets/gcpkms: Update plugin to v0.25.0
secrets/keymgmt: Update plugin to v0.20.1+ent
secrets/kmip: Update plugin to v0.20.0
secrets/kubernetes: Update plugin to v0.14.0
secrets/kv: Update plugin to v0.27.0
secrets/ldap (enterprise): Static roles will be migrated from a plugin-managed queue to the Vault Enterprise Rotation Manager system. Static role migration progress can be checked and managed through a new static-migration endpoint. See the LDAP documentation for more details on this process.
secrets/mongodbatlas: Update plugin to v0.18.0
secrets/openldap: Update plugin to v0.19.3+ent
secrets/pki: sign-verbatim endpoints no longer ignore basic constraints extension in CSRs, using them in generated certificates if isCA=false or returning an error if isCA=true
secrets/ssh: RSA key sizes are now limited to a maximum size of 8192 bits addressing CVE-2026-39829
secrets/terraform: Update plugin to v0.15.0
secure-plugin-api: Update to v0.2.0
storage: Upgrade aerospike client library to v8.
ui/secrets: Secrets engines url paths renamed from '/secrets' to '/secrets-engines'
ui: Remove HCP Link status indicator following deprecation of HCP Link.
ui: Remove ability to bulk delete secrets engines from the list view.
FEATURES:
Transform FF1 Support (Enterprise): Add support for the NIST approved FF1 format preserving encryption (FPE) algorithm, and a new rewrap operation to assist transitioning
from FF3-1 to FF1.
PKI External CA (Enterprise): A new plugin that provides the ability to acquire PKI certificates from Public CA providers through the ACME protocol
AI Agent Support (Beta/Enterprise): Adds beta support for first-class AI agents. Adds an Agent Registry to register agents, and adds support for using Vault as an OAuth resource server for registered agent entities. When configured, allows OAuth 2.0 JWTs to be used to directly authorize requests to Vault, without needing a Vault token.
AI Agent Support (Enterprise): Vault's support for first-class AI agents is now Generally Available. Adds an Agent Registry to register agents, and adds support for using Vault as an OAuth resource server for registered agent entities. When configured, allows OAuth 2.0 JWTs to be used to directly authorize requests to Vault, without needing a Vault token.
Agent Registry UI (Enterprise): Adds a new Agentic Security section to the primary navigation with an Agent Registry page where operators can view, search, and manage registered AI agents, their associated Vault entities and aliases, assigned policies, and operational status.
Automatic DNS-01 Challenge Fulfillment for PKI External CA: Integrate with the following DNS providers for automatic DNS-01 challenge fulfillment: AWS Route53, Azure DNS, Google Cloud DNS, and BIND and other RFC2136-compliant servers.
Automatic TLS Certificate Reloading: TCP listeners accept a new tls_reload_interval option. When set, Vault periodically checks tls_cert_file and tls_key_file for changes and reloads the certificate automatically, so rotated certificates are picked up without restarting the node or sending SIGHUP.
Billing metrics dashboard: Create a new billing dashboard with responsive layout to display metric data.
Dark Mode (beta): Added dark mode support to the Vault UI. Users can now choose between light, dark, or system-preferred themes from the Appearance section in user preferences.
Health Check Manager: Adds a dedicated system to manage and monitor the health of Vault Enterprise plugins. This provides operators and platform engineers with an explicit mechanism to verify connectivity and authentication against external systems.
IBM PAO License Integration: Added IBM PAO license support, allowing usage of Vault Enterprise with an IBM PAO license key. A new configuration stanza license_entitlement is required in the Vault config to use an IBM license. For more details, see the License documentation.
KMIP Bring Your Own CA: Add new API to manage multiple CAs for client verification and make it possible to import external CAs.
LDAP Secrets Engine Enterprise Plugin: Add the new LDAP Secrets Engine Enterprise plugin. This enterprise version adds support for self-managed static roles and Rotation Manager support for automatic static role rotation. New plugin configurations can be set as "self managed", skipping the requirement for a bindpass field and allowing static roles to use their own password to rotate their credential. Automated static role credential rotation supports fine-grained scheduled rotations and retry policies through Vault Enterprise.
LDAP Secrets Engine Rotate on Read (Enterprise): Add rotate-on-read support for static roles in the LDAP secrets engine, triggering an immediate credential rotation on read, with a configurable cooldown period and per-role override.
Login MFA TOTP Self-Enrollment (Enterprise): Simplify creation of login MFA TOTP credentials for users, allowing them to self-enroll MFA TOTP using a QR code (TOTP secret) generated during login. The new functionality is configurable on the TOTP login MFA method configuration screen and via the enable_self_enrollment parameter in the API.
ML-DSA Support in PKI: Add support for post-quantum signatures with ML-DSA keys in the PKI secrets engine.
Namespace (Enterprise): Add operator_namespace_path to listener configuration to restrict HTTP access to a specific namespace subtree, enabling per-listener namespace isolation.
PKI BYOK CA Key Migration (enterprise): A new sudo-protected POST /pki/keys/:uuid/export endpoint wraps a CA private key with a caller-supplied public key using RSA-OAEP-SHA256, ECDH-ES, or ML-KEM. The destination Vault instance can import the blob via POST /pki/keys/import using wrapped_key and export_key_hmac. Export events are recorded as tamper-evident audit records keyed on the SPKI fingerprint of the CA key, which survive delete-and-reimport cycles and surface as warnings on issuer reads.
PKI PKCS#12 and JKS Support: Adds support for PKCS#12 (PFX) and Java keytool (JKS) certificate bundles to relevant PKI endpoints. Bundles are returned as base64-encoded, password-protected files.
PKI Secure Key Export (Enterprise): Add export key management CRUD endpoint (LIST/WRITE/READ/DELETE /pki/export) to support secure CA private key migration between PKI mounts.
Plugins (Enterprise): Allow overriding pinned version when creating and updating database engines
Plugins (Enterprise): Allow overriding pinned version when enabling and tuning auth and secrets backends
Rotation Policies: Add support for automated rotation parameters to rotation policies
SCIM 2.0 Identity Provisioning Beta (Beta/Enterprise): Adds beta support for Vault to act as a SCIM 2.0 server, allowing external management of Vault entities, aliases and groups.
SCIM Token Support (Enterprise): Add support for SCIM tokens via token_type=scim with per-client active token limits and max TTL ceilings.
SLH-DSA support for Hybrid sign/verify in Transit engine (Enterprise): Add support for SLH-DSA as the PQC component for Hybrid sign/verify operations. This is compatible with both ECDSA (p-256, P-384, P-521) and Ed25519.
Secrets Sync UI: Added Workload Identity Federation (WIF) support in the UI for AWS, Azure, and GCP sync destinations
Secrets Sync UI: Adds support to sync Database static roles
Secrets Sync UI: Implements AWS KMS key ID and regional KMS keys support
Secrets Sync UI: Implements GCP replica regions and encryption support
Secrets engines UI catalog revamp: Redesigned view of secrets engines catalog when enabling an engine, adding more engine descriptors & ability to search the catalog for the ideal engine to utilize.
Telemetry Consent Banner: Add a consent banner allowing users to accept or decline anonymous usage data collection to help improve Vault.
Template Integration for PublicPKICA: Vault Agent templates are now automatically re-rendered when a PKI external CA certificate is issued or renewed.
Terraform Code Generator: Adds TFVP code snippets to ACL policy surfaces (show, flyout and form), powered by a new reusable mapping engine for generating HCL from Vault API payloads.
Transit Crypto Agility: Allows customers to alter cryptographic primitives in transit engine. This adds new endpoints /transit/keys/:name/algorithm and /transit/keys/:name/import_version.
UI ACL Policies intro: Onboarding intro which provides feature context to users.
UI Authentication methods intro: Onboarding intro which provides feature context to users.
UI Namespace Wizard (Enterprise): Onboarding wizard which provides advice to users based on their intended usage and guides them through namespace creation.
UI Policy Generator (Enterprise): Adds policy generator flyout to KV V2 and PKI secrets engines prepopulated with relevant API requests for each page.
UI Secret engines intro: Onboarding intro which provides feature context to users.
UI TLS Certificate login: Add UI login support for the TLS certificate (cert) authentication.
UI: Hashi-Built External Plugin Support: Recognize and support Hashi-built plugins when run as external binaries
UI: Hashi-Built External Plugin Support: Support external plugin version updates via the GUI.
UI: Mount versioned external plugins: Adds ability to mount previously registered, external plugins and specify a version when enabling secrets engines.
UI: PKI External CA: Adds views to inspect ACME orders (active orders by role, lookup by order ID or certificate), ACME account, DNS provider, and role configurations, and retrieve cached certificates.
User Preference Settings: Added a User Preferences page (/vault/<cluster>/user-preferences) accessible from the account menu. Includes a Data & Privacy section with a telemetry consent toggle that persists per-browser in localStorage.
Vault Agent: ACME protocol support: Add support to natively support Public CA ACME workflows
Vault Client (Enterprise): Introduce vault-client, a smaller binary that includes Vault Agent, Vault Proxy, and the CLI commands for interacting with a Vault server, but not the server itself. It is available as zip bundles and Alpine container images.
oauth-resource-server: Added oauth_denylist.entries.gauge metric to monitor active OAuth token denylist entries.
secrets-sync (enterprise): Added support for the Database secrets engine as a sync source, allowing static-role credentials to be synced to external destinations.
oauth-resource-server: Added OAuth Protected Resource Metadata endpoint (RFC 9728) for publishing authorization_details types and enabling automated discovery by Authorization Servers via /.well-known/oauth-protected-resource
secrets-sync: implemented workload identity federation support for secrets sync flows.
secrets: Added ability to view secrets in YAML format
IMPROVEMENTS:
Secrets Engines UI improvement: Updated configuration views and added tune support for configurations across all compatible secrets engines.
Sidebar UI improvement: Add top navbar, update sidebar navigation structure, and update page headers.
Update github.com/dvsekhvalnov/jose2go to fix security vulnerability CVE-2025-63811.
activity (enterprise): Add a cumulative namespace client count API at sys/internal/counters/activity/cumulative. For each namespace in the response it returns the sum of its own client counts and that of all its child namespaces.
agent-registry (enterprise): Add a local flag to agent registrations. When local=true, registrations are not replicated to other performance replication clusters and are kept local to the current cluster.
agent-registry (enterprise): Removed the restriction that disallowed the use of 'deny' in ceiling policies, resulting in request errors.
agent/pkiexternalca: Replace go.uber.org/atomic with sync/atomic (stdlib) for atomic boolean operations in the pkiexternalca package.
api: Add start_month and end_month parameters to /sys/billing/overview endpoint to allow querying billing data for specific time ranges.
api: Add a SHA256 sum field to the json list response for external plugins.
api: Add migration_done_at_epoch to sys/seal-status response.
api: Added sudo-permissioned sys/reporting/scan endpoint which will output a set of files containing information about Vault state to the location specified by the reporting_scan_directory config item.
auth/aws: Added missing OpenAPI metadata for the aws auth endpoints
auth/aws: Migrate the AWS auth method, its public API client (api/auth/aws), and the shared login-data helper (internal/awsutil/v2) from AWS SDK for Go v1 to v2.
auth/cert: Support login via x-forwarded cert headers even with tls disabled on the vault listener.
auth/jwt (OAuth RS): Add EdDSA/Ed25519 support to the OAuth resource server JWT validation path. Ed25519 public keys can now be registered via public_keys and supported_algorithms = ["EdDSA"] is now accepted at configuration time and runtime.
auth/jwt: Add parameter constraint fields (allowed_parameters, denied_parameters, required_parameters) to vault:path_access RAR type schema and metadata for complete OAuth Resource Authorization Request support
auth/ldap: Require non-empty passwords on login command to prevent unauthenticated access to Vault.
auth/okta: Add missing OpenAPI path description for the /auth/{okta_mount_path}/verify/{nonce} path.
auth/okta: Added missing OpenAPI metadata for auth Okta plugin endpoints
auth/spiffe (enterprise): Add SPIFFE login cli handler.
auth/token: Add global denylist for revoking OAuth JWTs to prevent authorization of specific tokens across all namespaces.
auth/token: Add the revoke-oauth endpoint to revoke an external OAuth token by its issuer and unique ID.
auth/token: auth/token/revoke-accessor now supports revoking JWT tokens by accessor
ci (enterprise): Upload build stage duration metrics to Instana for CI observability.
cli: Move spiffe and tpm CLI login methods to CE.
command/agent: Migrate AWS client from aws-sdk-go v1 to aws-sdk-go-v2.
config/listener: logs warnings on invalid x-forwarded-for configurations.
consumption-billing: Add a new sys/billing/config endpoint to allow configuration of billing data retention (min 13 months, max 6 years).
consumption-billing: Add billing tracking for LDAP and OpenLDAP service account
library sets as part of both HWM role metrics and running-count product usage metric.
consumption-billing: Add billing tracking for OS Local Account static roles to support consumption-based billing metrics and high-water mark (HWM) tracking.
consumption-billing: Added consumption billing metrics for GCP KMS data protection operations.
consumption-billing: Added consumption billing metrics for OIDC tokens.
consumption-billing: Added consumption billing metrics for PKI External CA certificates.
consumption-billing: Added consumption billing metrics for SPIFFE JWT tokens.
consumption-billing: Adds a new sys/billing/overview endpoint that returns current and previous month consumption billing metrics. Accessible via API client method client.Sys().BillingOverview().
consumption-billing: Enabled sys/billing/overview endpoint in admin namespace.
consumption-billing: Float64 values returned by sys/billing/overview are now rounded to 4 decimal places.
consumption-billing: Increased billing data retention from 2 months to 37 months. The /sys/internal/billing/overview API endpoint now returns 37 months of historical consumption billing data by default.
consumption-billing: Mount attribution data is now stored for consumption billing metrics. The retention period can be configured via the new attribution_retention_months parameter on sys/billing/config (0–72 months, default 37). Setting to 0 disables attribution storage and immediately wipes all existing attribution data.
consumption-billing: The /sys/internal/billing/overview API endpoint now always returns all metric types in the response, even when their values are zero. This ensures consistent response structure for easier client-side parsing.
core (enterprise): Make deadlock detection in sealwrap configurable by adding "sealwrap" to existing configuration detect_deadlocks.
core (enterprise): Sanitized config now shows kms_library config.
core (enterprise): Add OAuth resource server authorization_details type discovery endpoints and align vault:path_access claim matching semantics with path/capabilities evaluation; discovery endpoints are unauthenticated.
core (enterprise): Add disallow_env_vars in PKCS#11 to allow per key configuration for RSA encryption algorithm.
core (enterprise): Add sys/config/ui/checklist-state endpoint to persist and retrieve onboarding checklist progress.
core (enterprise): Add an endpoint at sys/config/oauth-resource-server/id/:config_id to read oauth resource server profiles by config_id
core (enterprise): Add common_criteria_mode feature_flags setting which limits listener TLS cipher suites.
core (enterprise): Added a new telemetry metric vault.core.license.termination_time_epoch.
core (enterprise): Make OAuth resource server JWT typ validation more permissive for tokens from IdPs such as Okta by allowing a missing typ header, while restricting present typ values to at+jwt, application/at+jwt, and JWT.
core (enterprise): allow secretmounts' seal wrap configuration to be changed via auth and/or mount tune instead of only at mount creation.
core (enterprise): enable rotation manager to send rotation information required by plugin backends during registration and rotation operations. This allows plugin backends to have the necessary context for managing their rotation state effectively.
core (enterprise): enable rotation manager to use configurable retry policies to limit the retry behavior for rotation entries and include an orphaning mechanism to handle entries that exceed the maximum retry attempts.
core (enterprise): improve rotation manager error handling by implementing a backoff when re-queueing failed rotations
core (enterprise): Ameriolate sealwrap lock contention for core paths.
core/acl: Adds a global deny_slash_in_templated_path configuration option to reject the presence of slashes in rendered identity templates in policies, defaulting to false.
core/census: Add vault.secret.engine.transform.role.count product usage metric reporting the number of Transform secret engine roles.
core/census: Add product usage metrics vault.auth.method.cert.role.count, vault.auth.method.cert.crl.count, vault.auth.method.spiffe.role.count, and vault.auth.method.scep.role.count reporting the number of Cert auth roles and CRLs, SPIFFE auth roles, and SCEP auth roles across all namespaces and mounts, and vault.auth.method.spiffe_enabled reporting whether the SPIFFE auth method is enabled.
core/census: Add product usage metrics reporting the number of Transform secret engine transformations, templates, alphabets, and stores, and KMIP secret engine scopes, scope roles, and CAs.
core/identity: Add two new fields to the alias API, external_id and issuer. These fields do not inherently do anything meaningful, and are part of a future feature.
core/identity: Adds a global deny_slash_in_templated_path configuration option to reject the presence of slashes in rendered identity templates in policies, defaulting to false.
core/managed-keys (enterprise): Allow GCP managed keys to leverage workload identity federation credentials
core/managed-keys/PKCS#11 (enterprise): Add PKCS#11 backend parameter rsa_oaep_hash to use for RSA-OAEP encryption with CKM_RSA_PKCS_OAEP mechanism.
core/managed-keys/PKCS#11 (enterprise): Providing a non-empty value for one field while the other is already saved is rejected. To switch addressing modes, you must explicitly clear the old field by sending it as an empty string ("") in the same request alongside the new value.
core/managed-keys/PKCS#11 (enterprise): slot and token_label are now strictly enforced as mutually exclusive identifiers for an HSM token
core/metrics: Reading and listing from a snapshot are now tracked via the vault.route.read-snapshot.{mount_point} and vault.route.list-snapshot.{mount_point} metrics.
core/oauth-resource-server (enterprise): Read and list responses for sys/config/oauth-resource-server now include a mount_accessor field containing the pre-assembled synthetic accessor string (oauth-resource-server_<namespace_id>_<config_id>). This is the accessor reported for profile-backed aliases in identity and audit output, and the value used to select those aliases in templated policies.
core/oauth-resource-server (enterprise): Support setting an alternate claim name in an OAuth Resource Configuration specifying where to read authorization details in a presented JWT. New option "authorization_details_claim" defaults to "authorization_details".
core/oauth-resource-server (enterprise): The list response for sys/config/oauth-resource-server now includes a key_info map keyed by profile name, each entry carrying config_id and mount_accessor. Listed profile names are now sorted, and profiles whose details cannot be read are reported in a response warning.
core/oauth-resource-server: Support data locality for OAuth Resource Server configuration profiles (non-replicated profiles).
core/seal (enterprise): Make it possible for new nodes to join a cluster configured with Seal High Availability.
core/seal (enterprise): Update Oracle Cloud library to enable seal integration with newer regions.
core/seal: Enhance sys/seal-backend-status to provide more information about seal backends.
core: Add a ui_settings configuration stanza with a ui_telemetry option, surfaced to the UI via the sys/internal/ui/settings endpoint, that gates anonymous UI usage telemetry.
core: Automatically write a goroutine dump to a temp directory on shutdown (SIGTERM/SIGINT). The output directory can be overridden with VAULT_STACKTRACE_FILE_PATH, and the dump can be suppressed with the config field disable_goroutine_trace_dump.
core: Enforce OAuth authorization_details vault:path_access constraints with strict path/capabilities and parameter-level controls.
core: Improve goroutine termination during preseal.
core: check rotation manager queue every 5 seconds instead of 10 seconds to improve responsiveness
dockerfile: container will now run as vault user by default
events (enterprise): Add event notifications support for lease events.
events (enterprise): Forward event notifications from primary to secondary clusters
events: Add VAULT_EVENT_NOTIFICATIONS_BOUNDED_QUEUE_SIZE environment variable to configure bounded event queues for event notification subscribers. Set to a positive integer (e.g., 16) to enable buffered channels of that size (maximum 1000). This prevents resource exhaustion in deployments with high subscriber counts, but comes at the cost of the potential for subscribers to miss events. Defaults to 0 (unbuffered) for backward compatibility.
events/sqs: Migrate SQS event subscription plugin from aws-sdk-go v1 to aws-sdk-go-v2.
go: update to golang/x/crypto to v0.45.0 to resolve GHSA-f6x5-jh6r-wrfv, GHSA-j5w8-q4qc-rx2x, GO-2025-4134 and GO-2025-4135.
identity/entity-alias: Added profile_name and config_id fields as shortcuts to resolve an OAuth Resource Server profile when creating entity aliases, without requiring a mount_accessor. Resolving a profile also binds the alias to that profile's issuer, which OAuth Resource Server authentication requires. The fields are mutually exclusive with each other and with mount_accessor.
identity/scim (enterprise): Add POST identity/scim/client/<client-name>/link-entity endpoint to re-establish SCIM ownership over an unmanaged entity, restoring managed aliases and group memberships.
identity/scim (enterprise): Add POST identity/scim/client/<client-name>/link-group and POST identity/scim/client/<client-name>/unlink-group admin endpoints. link-group transfers ownership of an existing unmanaged Vault identity group to the named SCIM client; all current group members must already be owned by that client. unlink-group removes SCIM ownership from a group the client currently owns, returning it to unmanaged status.
identity/scim (enterprise): Add POST identity/scim/client/<client-name>/unlink-entity endpoint to remove the SCIM ownership link from an entity without deleting it.
identity/scim (enterprise): Add allow_user_adoption field to SCIM client configuration. When set to true, a POST /Users request whose userName matches an existing login alias will adopt the pre-existing entity rather than returning a conflict. Defaults to false.
identity/scim (enterprise): Add support for attributes and excludedAttributes query parameters on SCIM User and Group endpoints, allowing callers to request a subset or exclusion of attributes in responses per RFC 7644.
identity/scim (enterprise): Added filtering support to the GET /scim/v2/Users and GET /scim/v2/Groups endpoints per RFC 7644. Supported filters: userName eq, externalId eq, active eq, and meta.lastModified gt/ge/lt/le for Users; displayName eq and meta.lastModified gt/ge/lt/le for Groups. Unsupported filter expressions return HTTP 400. ServiceProviderConfig now advertises filter.supported: true.
identity/scim (enterprise): Fix Group PATCH to support filtered member paths of the form members[value eq "uuid"] for add and replace operations, matching the path format already supported for remove. This resolves an Okta error ("unsupported path") during Group Push membership updates. Group ownership mismatches now return 403 Forbidden (previously 404 Not Found); attempting to add/replace members owned by a different SCIM client now returns 403 (previously 400 with a not found-style detail).
identity/scim (enterprise): Improve SCIM User and Group listing endpoint performance by using prefix sort instead of a separate sort pass.
identity/scim (enterprise): Renamed the unlink_aliases consent parameter to unlink_secondary_aliases and separated the response payload into unlinked_main_alias_id and unlinked_secondary_alias_ids.
identity/scim (enterprise): The 2.1 User extension now supports a client-managed aliases attribute. SCIM clients can push an array of {mount_accessor, name} entries on POST, PUT, and PATCH /Users to create, rename, or remove secondary aliases on an entity beyond the primary alias controlled by alias_mount_accessor.
identity/scim (enterprise): Update PATCH operations on scim/v2/Users to allow multiple modifications in the same patch call, support for patch operations on user metadata and name in addition to active status, and allow specifying path value in patch operations
identity/scim: New SCIM extensions for Users and Groups are supported, but mutually exclusive with User metadata extension.
identity/scim: POST /Users for a client with alias_mount_accessor now adopts a pre-existing entity when the userName matches an existing login alias on the target mount, instead of failing with a conflict.
identity/scim: Unmanaged groups (no SCIM owner) are now visible to all SCIM clients via GET /Groups and GET /Groups/. Groups owned by a different client remain hidden (403 on direct read). For unmanaged groups, the members array is filtered on read to only the members owned by the requesting client.
identity/scim: externalId is now optional on POST /Users and is no longer required to be unique within a namespace. Multiple users may share the same externalId value.
identity/scim: permit adoption of unmanaged Vault groups only on PUT or PATCH SCIM requests.
identity: Include entity status and entity/alias timestamp details in entity list key_info responses.
jwt/oauth-resource-server: Profile resolution now walks the namespace ancestor chain, allowing a JWT whose OAuth Resource Server Configuration Profile is registered in a parent namespace to authenticate requests targeting resources in child namespaces.
kmip (enterprise): Add experimental API to execute KMIP requests.
license utilization reporting (enterprise): Add metrics for the number of issued PKI certificates.
license utilization reporting (enterprise): Utilization reports now include new license metadata fields issuer, edition, add_ons, license_start_time, license_expiration_time, and license_termination_time.
license utilization reporting: Added consumption billing metrics.
oauth-resource-server: Add support for fine-grained policy control options (parameter constraints) in Rich Authorization Requests (RAR), including allowed_parameters, denied_parameters, and required_parameters inside authorization_details.
oauth-resource-server: Add support for identity template expressions (e.g. {{identity.entity.id}}) in Rich Authorization Requests (RAR).
oauth-resource-server: Improved error body returned when permission is denied by ceiling policies to indicate that ceiling policies were what denied the request (CEILING_POLICY_DENIED).
pki: Reject obviously unsafe validation targets during ACME HTTP-01 and TLS-ALPN-01 challenge verification
policies: add warning about list comparison when using allowed_parameters or denied_parameters
product usage reporting (enterprise): Add vault.secure_hub_connected Census product usage metric to report whether a cluster is connected to the Secure Hub.
rotation: Ensure rotations for shared paths only execute on the Primary cluster's active node. Ensure rotations for local paths execute on the cluster-local active node.
scim: The SCIM Group PATCH handler now supports the path field in the form members[value eq "id"] on remove operations.
scim: User resources now include a read-only groups field listing the direct group memberships managed by the requesting SCIM client, per RFC 7643.
sdk/helper/keysutil: The lock manager's GetPolicy function now always returns a locked Policy, even when caching is enabled. The PolicyRequest struct has a new field to indicate whether the caller requires a write lock on the policy.
sdk/rotation: Prevent rotation attempts on read-only storage
sdk: Add NewTestDockerCluster support for running external plugins within the same container as the server. Also add support for those plugins to expose their own listeners, as KMIP does.
sdk: Add alias_metadata to tokenutil fields that auth method roles use.
sdk: Expand support for docker test cluster options like seals, kms libraries, and entropy augmentation. DockerClusterNode.UpdateConfig now takes a full set of cluster options instead of just node config.
sdk: add WIF and rotation helpers for checking if params were updated to allow the consumer to know when changes need to be persisted to storage
secret-sync (enterprise): Added telemetry counters for reconciliation loop operations, including the number of corrections detected, retry attempts, and operation outcomes (success or failure with internal/external cause labels).
secret-sync (enterprise): Added telemetry counters for sync/unsync operations with status breakdown by destination type, and exposed operation counters in the destinations list API response.
secret-sync: add parallelization support to sync and unsync operations for secret-key granularity associations
secrets import: Add support for allowed_ipv4_cidrs in source_aws and source_azure configuration blocks to allow connections to explicitly permitted private IPv4 ranges.
secrets-pki (enterprise): Add response data in a parsed format to the audit log for enrollment protocols.
secrets-sync (enterprise): Added support for a boolean force_delete flag (default: false). When set to true, this flag allows deletion of a destination even if its associations cannot be unsynced. This option should be used only as a last-resort deletion mechanism, as any secrets already synced to the external provider will remain orphaned and require manual cleanup.
secrets-sync (enterprise): Improved the user experience during mount lifecycle changes by triggering immediate unsyncing of external secrets when a secrets engine mount is deleted or disabled. By moving this logic from the background reconciliation loop to a direct callback, the system prevents perceived "leaks" and ensures external secret resources are cleaned up synchronously with the Vault unmount.
secrets-sync: Adds support for customer-controlled (CSP Managed) encryption in secrets sync flows for AWS destination.
secrets/aws: Added missing OpenAPI metadata for the aws secret engine endpoints
secrets/aws: Migrate AWS client from aws-sdk-go v1 to aws-sdk-go-v2.
secrets/database: Add root rotation support for Snowflake database secrets engines using key-pair credentials.
secrets/keymgmt (enterprise): Add support for multi-region AWS KMS keys.
secrets/kmip (enterprise): Obey configured best_effort_wal_wait_duration when forwarding kmip requests.
secrets/kv (enterprise): Support reading and recovering KVv2 secrets from a loaded snapshot, including in-place recover and copy-from-path within the same mount and namespace.
secrets/ldap: Users can now fully manage and tune the LDAP secrets engine. This includes the ability to view, edit, and configure the LDAP engine.
secrets/pki (enterprise): Allow SCEP to use an issuer that is backed by an RSA based PKCS#11 managed key
secrets/pki (enterprise): Return the POSTPKIOperation capability within SCEP GetCACaps endpoint for better legacy client support.
secrets/pki (enterprise): Validate entire chain in common criteria mode; add field to enable time checks on validation
secrets/pki (enterprise): When the commo Similar to Hashicorp with recent updates:
- Anthropic release notes964 release notes · Latest Nov 18, 2026
- Cursor release notes144 release notes · Latest Nov 6, 2026
- GitHub release notes1190 release notes · Latest Nov 18, 2026
- Smokeball release notes149 release notes · Latest Nov 11, 2026
- Cosmolex release notes20 release notes · Latest Jul 30, 2025
- PracticePanther release notes37 release notes · Latest Oct 27, 2026
- Oct 14, 2026
- Date parsed from source:Oct 14, 2026
- First seen by Releasebot:Oct 14, 2026
v1.16.6
Terraform 1.16.6 fixes workspace discovery with uppercase tag keys and addresses an HTTP/2 resource exhaustion vulnerability.
1.16.6 (October 14, 2026)
BUG FIXES
- cloud: terraform init can now find workspaces selected by key/value tags whose keys contain uppercase letters. (#39306)
- test: Allow module under test to use deprecated outputs. (#39207)
NOTES
- Prevent a HTTP/2 resource exhaustion via CVE-2026-78669. Exploitation would require a compromised (untrusted) provider/module registry. Such a threat is considered to be outside the perimeter of Terraform core security guarantees. (#39375)
- Oct 14, 2026
- Date parsed from source:Oct 14, 2026
- First seen by Releasebot:Sep 10, 2026
- Modified by Releasebot:Nov 11, 2026
v1.17.0-rc2
Terraform releases 1.17.0-rc2 with general availability for Terraform Policy, support for variables and locals in provider requirements, and a minimal-refresh planning option. The update also improves testing and diagnostics while fixing issues across queries, functions, and plan display.
1.17.0-rc2 (October 14, 2026)
NEW FEATURES:
- Terraform now supports variables and locals in provider requirements (#39153)
- A new -minimal-refresh planning option has been added, which will only refresh resources that have proposed changes. (#35290)
- policy: Terraform Policy is now generally available. The -policies flag for plan, apply, and query no longer requires an experimental build or the -allow-experimental-features flag. Query policies evaluate resources discovered by list blocks and report human-readable or JSON results. See https://developer.hashicorp.com/terraform/policy for more information. (#38970)
ENHANCEMENTS:
- command/init: Enrich log messages with provider versions (#38918)
- test: Add mock_provider support for ephemeral resources (#38928)
- command/login: display warning after successful login if user is subject to an organization's TTL policy
BUG FIXES:
- funcs: pow and log no longer panic when result is not a number (#38912)
- ephemeral: Terraform will now use and display diagnostics raised when renewing an ephemeral resource. This may cause warnings to appear that previously were lost. We expect that any error diagnostics that were previously lost would have caused confusing downstream errors, so we do not anticipate this change to be breaking. (#38989)
- test: Deterministic dependency ordering in cleanup graph (#38247)
- query: report Unknown and N/A results for policy evaluations of discovered resources (#39058)
- query: terraform query -policies now rejects a path that is not a directory, instead of passing it on to the policy engine (#39238)
- funcs: The log and pow functions now raise errors when they return +/- Infinity, as this result is not usable in downstream code. (#39304)
- show: Read variable values from the plan file when showing a local plan (#39362)
NOTES:
- version: JSON output now includes a new format_version field, which will enable safer future changes of the command's JSON output format. It is assumed existing tooling ignores unknown fields and therefore this change should not be breaking in itself but we advice consumers to pay attention to format_version in future releases and/or use latest version of hashicorp/terraform-json & hashicorp/terraform-exec which does. (#38930)
Previous Releases
For information on prior major and minor releases, refer to their changelogs:
- v1.16
- v1.15
- v1.14
- v1.13
- v1.12
- v1.11
- v1.10
- v1.9
- v1.8
- v1.7
- v1.6
- v1.5
- v1.4
- v1.3
- v1.2
- v1.1
- v1.0
- v0.15
- v0.14
- v0.13
- v0.12
- v0.11 and earlier
- Oct 8, 2026
- Date parsed from source:Oct 8, 2026
- First seen by Releasebot:Oct 16, 2026
v2.2.0-rc1
Vault releases a major update featuring generally available AI agent support, expanded PKI and post-quantum cryptography, automated LDAP credential rotation, and new billing and UI capabilities. The release also strengthens security, identity controls, and operational safeguards.
October 07, 2026
Original source
BREAKING CHANGES:
containers: Remove cap_ipc_lock capability on vault at build time to allow running Vault in common container runtimes. Vault in containers will no longer be able to call mlock() to lock memory. Operators should set disable_mlock = true in Vault's configuration. Runtime operators are advised to disable swapping to guarantee data safety.
containers: The following packages have been removed from UBI based container images: gnupg, openssl, procps.
containers: set cap_ipc_lock capability on vault at build time. Container runtimes will need to add IPC_LOCK capabilities when running the vault container.
physical/postgresql: breaking change - PostgreSQL storage backend authentication now prefers Azure Workload Identity over Managed Identity. Update go-pgmultiauth to v1.1.0. Existing Managed Identity-based PostgreSQL configurations may stop working if Workload Identity is configured. Affected users must migrate PostgreSQL authentication to Workload Identity.
pki: ACME finalization with the default sign-verbatim directory policy now rejects CSRs that contain URI SANs, email SANs, or Other SANs. ACME challenges only verify DNS names and IP addresses; those SAN types are never validated and must not appear in issued certificates. Operators who require the previous behaviour can set default_directory_policy = "sign-verbatim-unsafe" in config/acme, accepting that the resulting certificates may contain unverified identity claims.
sdk/helpers/docker: Migrate docker helpers from github.com/docker/docker to github.com/moby/moby. This was necessary as github.com/docker/docker is no longer maintained. Resolves GHSA-x744-4wpc-v9h2 and GHSA-pxq6-2prw-chj9.
SECURITY:
Upgrade cloudflare/circl to v1.6.3 to resolve CVE-2026-1229
Upgrade filippo.io/edwards25519 to v1.1.1 to resolve GO-2026-4503
acl: Fix privilege-escalation vulnerability where a denied_parameters constraint on the policies request field could be bypassed by submitting a mixed-case policy name (e.g. "Super-Admin" instead of "super-admin"). Vault now normalizes the policies parameter to lowercase before evaluating allowed_parameters/denied_parameters constraints.
api/auth/gcp: Update go.opentelemetry.io/otel/sdk to fix CVE-2026-39883.
api/auth: Update github.com/go-jose/go-jose to fix security vulnerability CVE-2026-34986 and GHSA-78h2-9frx-2jm8.
api: Update golang.org/x/net to resolve GO-2026-4918
auth/aws: Fix an issue where a user may be able to bypass authentication to Vault due to incorrect caching of the AWS client
auth/cert: Ensure that the certificate being renewed matches the certificate attached to the session.
auth/radius: Added case_insensitive_names toggle to prevent username collisions and enable case-insensitive user handling.
core (enterprise): Prevent policy-name canonicalization bypasses in ACL parameter restrictions.
core/acl: Fix LIST ACL bypass where a trailing-slash request could skip a more-specific deny rule.
core/identity: Reject wildcards in rendered identity templates.
core/plugin: Fix plugin catalog entries restored from a raft snapshot, written through sys/raw, or replicated being able to run a binary outside plugin_directory.
core/policy: Harden request-time ACL construction to ignore malformed legacy policy references containing path-navigation segments (. or ..) so traversal-style names are never resolved or applied.
core: Correctly remove any Vault tokens from the Authorization header when this header is forwarded to plugin backends. The header will only be forwarded if "Authorization" is explicitly included in the list of passthrough request headers.
core: Fixed a bypass of exact-deny ACL policies where case-variant AppRole, AWS, Azure, GCP, Kubernetes, SCEP, or TPM role names, GitHub team or user policy mapping keys, certificate or CRL names, ACL/RGP/EGP policy names, or userpass usernames could evade the deny and be resolved by the backend to the same protected resource. Okta group names, LDAP and RADIUS names on mounts left in their default case-insensitive configuration, and Enterprise SCIM client names (identity/scim/client/<name>, where a case-variant write overwrites the existing client) are not covered by this fix and remain subject to the same bypass; avoid combining a wildcard allow with an exact deny on those mounts and paths.
core: Resolve GHSA-j88v-2chj-qfwx by removing our dependency on github.com/jackc/pgx/v3 and github.com/jackc/pgx/v4
core: Resolve GO-2026-4518 and GHSA-jqcq-xjh3-6g23 by upgrading to github.com/jackc/pgx/v5
core: Update github.com/Azure/go-ntlmssp to fix security vulnerability v0.1.1.
core: Update github.com/apache/thrift to fix security vulnerability GHSA-wf45-q9ch-q8gh
core: Update github.com/apache/thrift to v0.24.0 to fix security vulnerability GHSA-8wv5-x4w7-5gww.
core: Update github.com/aws/aws-sdk-go-v2/ to fix security vulnerability GHSA-xmrv-pmrh-hhx2.
core: Update github.com/go-jose/go-jose to fix security vulnerability CVE-2026-34986 and GHSA-78h2-9frx-2jm8.
core: Update github.com/hashicorp/go-getter to fix security vulnerability GHSA-92mm-2pjq-r785.
core: Update github.com/jackc/pgx/v5 to fix security vulnerability GHSA-j88v-2chj-qfwx.
core: Update go.etcd.io/etcd/client/pkg/v3 to v3.7.1 to fix security vulnerability GO-2026-6107.
core: Update go.opentelemetry.io/otel/sdk to fix CVE-2026-39883.
core: Update golang.org/x/crypto to v0.56.0 to fix security vulnerabilities GO-2026-6354 and GO-2026-6355.
core: Update golang.org/x/net to resolve GO-2026-4918"
core: Update google.golang.org/grpc to v1.83.2 to fix security vulnerability GHSA-2v4p-qf9q-27wj.
core: Update software.sslmate.com/src/go-pkcs12 to v0.7.2 to fix security vulnerability GO-2026-5052.
core: Use constant-time recovery token comparison.
core: Validate both path and file_path cannot be empty for requests to sys/audit/{path}
core: Reject URL-encoded paths that do not specify a canonical path.
http: Add configurable max_token_header_size listener option (default 8 KB) to bound the size of authentication token headers (X-Vault-Token and Authorization: Bearer), preventing a potential denial-of-service attack via oversized header contents. The stdlib-level MaxHeaderBytes backstop is also now set on the HTTP server. Set max_token_header_size = -1 to disable the limit.
identity/scim (enterprise): The identity/entity/merge endpoint now rejects requests that involve any SCIM-managed entity, preventing privileged operators from bypassing SCIM ownership guardrails to transfer aliases, group memberships, or policies across SCIM boundaries.
identity: Prevent the entity batch-delete endpoint (identity/entity/batch-delete) from deleting the underlying storage of entities that belong to another namespace.
identity: Entity name updates now reject mismatched id or external_id selectors to prevent retargeting updates to a different entity.
sdk: Resolve GHSA-j88v-2chj-qfwx by removing our dependency on github.com/jackc/pgx/v3 and github.com/jackc/pgx/v4
sdk: Resolve GO-2026-4518 and GHSA-jqcq-xjh3-6g23 by upgrading to github.com/jackc/pgx/v5
sdk: Update github.com/Azure/go-ntlmssp to fix security vulnerability v0.1.1.
sdk: Update github.com/go-jose/go-jose to fix security vulnerability CVE-2026-34986 and GHSA-78h2-9frx-2jm8.
sdk: Update github.com/jackc/pgx/v5 to fix security vulnerability GHSA-j88v-2chj-qfwx.
sdk: Update golang.org/x/net to resolve GO-2026-4918"
secrets/spiffe (enterprise): Ensure template values are properly escaped.
transform (enterprise): Add appropriate db specific quoting and escaping.
ui: Upgrade dompurify to 3.4.0
ui: Disable scarf analytics for ui builds.
vault/sdk: Upgrade cloudflare/circl to v1.6.3 to resolve CVE-2026-1229
vault/sdk: Upgrade go.opentelemetry.io/otel/sdk to v1.40.0 to resolve GO-2026-4394
CHANGES:
License: Add Agentic IAM terms to client licensing model and update terms for Vault Platform licensing model.
audit: A new top-level key called supplemental_audit_data can now appear within audit entries of type "response" within the request and response data structures. These new fields can contain data that further describe the request/response data and are mainly used for non-JSON based requests and responses to help auditing. The audit-non-hmac-request-keys and audit-non-hmac-response-keys apply to keys within supplemental_audit_data to remove the HMAC of the field values if so desired.
auth/alicloud: Update plugin to v0.24.0
auth/azure: Update plugin to v0.25.1
auth/cf: Update plugin to v0.24.0
auth/gcp: Update plugin to v0.24.1
auth/jwt: Update plugin to v0.27.1
auth/kerberos: Update plugin to v0.18.0
auth/kubernetes: Update plugin to v0.25.0
auth/oci: Update plugin to v0.22.0
auth/saml: Update plugin to v0.9.0
auth/token: JWT revocation via auth/token/revoke-self and auth/token/revoke-accessor is no longer supported. auth/token/revoke and auth/token/revoke-orphan now require the full JWT to revoke an OAuth JWT and reject the internal stored JWT ID form. Non-JWT Vault token behavior is unchanged.
cli/status: vault status no longer forces the root namespace when querying seal status. It now respects the namespace set via VAULT_NAMESPACE or the -namespace flag, consistent with other CLI commands.
core/acl: LIST requests with a trailing slash now correctly respect more-specific deny policies. Previously, a deny on path "kv/" { deny } could be bypassed for LIST kv/private/ if a broader allow path "kv/" also existed. Policies relying on the previous (incorrect) behavior may now be denied.
core/managed-keys (enterprise): The response to API endpoint GET sys/managed-keys/:type/:name now
returns an array of string values for key usages, rather than an array of integer values. The strings used are 'encrypt' (1), 'decrypt' (2), 'sign' (3), 'verify' (4), 'wrap' (5), 'unwrap' (6), 'generate_random' (7), and 'mac' (8).
core/oauth-resource-server (enterprise): The write response for sys/config/oauth-resource-server/:name now returns HTTP 200 with the full profile object instead of HTTP 204 with an empty body. Validation warnings are returned alongside the profile data rather than in place of it.
core/plugin: Plugin catalog entries are now checked against plugin_directory whenever they are used, not only at registration. An entry whose command resolves outside the directory, including through a symlink, is refused with plugin command is outside of configured plugin directory, and mounts that use it are skipped at startup while keeping their data. Such plugins must be registered again with their binary inside plugin_directory.
core/policy: Vault now validates policy names with segment-aware checks. Empty names and names containing . or .. path segments are rejected for new policy writes and assignments, while names containing / and \ remain supported. During request-time ACL construction, legacy traversal-style policy references are not applied (treated as invalid and unresolved), which can reduce effective token permissions. Operators should audit and rename affected policies before upgrading.
core/raft: Limited concurrent retry-join workers to 20. Any further retry-join attempts while 20 are in progress will result in an error (too many concurrent raft retry joins in progress).
core: ACL and Sentinel EGP rule paths targeting a specific AppRole, AWS, Azure, GCP, Kubernetes, SCEP, or TPM role, GitHub team or user policy mapping key, certificate or CRL name, ACL/RGP/EGP policy name, or userpass username are now matched against the lowercased resource name, since these backends resolve those names case-insensitively. A rule written with a mixed-case resource name (for example auth/approle/role/MyRole) no longer matches requests for that resource and must be rewritten using the lowercase name (auth/approle/role/myrole). The lowercased form is also what Sentinel RGP and EGP policies observe as request.path, so policy rules that compare that value against a mixed-case path (for example request.path is "auth/approle/role/MyRole") must be updated as well. External auth and secret plugins are not affected by this normalization and continue to receive requests with their original casing. Existing deny rules using mixed-case resource names will fail open (become allow-all) after upgrade until rewritten with lowercase names.
core: Bump Go version to 1.27.1.
core: Require sudo capability for sys/mounts/auth/<path>/tune, matching sys/auth/<path>/tune.
core: Vault now rejects paths that are not canonical, such as paths containing double slashes (path//to/resource)
core: Vault will now redirect non-canonicalized paths (containing /./, /../, or //) to a cleaned path, instead of rejecting these requests
core: bump github.com/hashicorp/cap to v0.12.0
core: remove support for duplicate attributes in HCL configuration files and policy definitions. Parsing HCL with duplicate attributes now always fails, and the VAULT_ALLOW_PENDING_REMOVAL_DUPLICATE_HCL_ATTRIBUTES environment variable that previously restored the legacy behavior has been removed.
core: secondary DR requests can now be authenticated using a root token generated on the primary.
core: sys/generate-root and sys/replication/dr/secondary/generate-operation-token endpoints are now authenticated by default, with the old unauthenticated behaviour enabled by setting the new HCL config key enable_unauthenticated_access to include the value "generate-root" or "generate-operation-token" respectively.
core: sys/rekey endpoints are now authenticated by default, with the old unauthenticated behaviour enabled by setting the new HCL config key enable_unauthenticated_access to include the value "rekey".
database/couchbase: Update plugin to v0.17.0
database/elasticsearch: Update plugin to v0.21.0
database/mongodbatlas: Update plugin to v0.18.0
database/redis-elasticache: Update plugin to v0.9.1
database/redis: Update plugin to v0.9.0
database/snowflake: Update plugin to v0.17.0
http: Return 431 status code instead of 400 when token header size validation fails.
identity/scim (enterprise): Added "allow_group_adoption" toggle to allow or forbid a SCIM client from adopting groups.
identity/scim (enterprise): Added a check for case-duplicate identity resources which, if detected, will cause the SCIM operation to fail with an error message. To deduplicate identities, please use the force-identity-deduplication activation flag.
identity/scim (enterprise): Loading SCIM clients will now test for and remove duplicate client names. SCIM clients are now properly case insensitive.
identity/scim: Remove the SCIM activation flag; SCIM v2 endpoints are now always available without prior activation
identity: Require sudo capability to invoke the identity entity merge API endpoint (identity/entity/merge).
license utilization reporting (enterprise): Manual reporting bundles generated by vault operator utilization have a changed format. Notably they contain an array of snapshot_records instead of snapshots. The decoded_snapshot field in each record contains the human-readable data that was previously in the snapshots array.
mfa/duo: Upgrade duo_api_golang client to 0.2.0 to include the new Duo certificate authorities
oauth-resource-server: Prevent issuer_id from being mutated after OAuth Resource Server profile creation. Operators must delete and recreate profiles to change the issuer_id.
oauth-resource-server: Prevent unique_id_claim from being mutated after OAuth Resource Server profile creation. Operators must delete and recreate profiles to change the unique_id_claim.
oauth-resource-server: The OAuth Resource Server feature no longer requires activation via the sys/activation-flags/oauth-resource-server/activate endpoint.
oauth-resource-server: Update OAuth Resource Server config to include custom claim options for the token's unique identifier and actor.
packaging: Container images are now exported using a compressed OCI image layout.
packaging: UBI container images are now built on the UBI 10 minimal image.
secrets/ad: Update plugin to v0.23.0
secrets/alicloud: Update plugin to v0.23.0
secrets/azure: Update azure enterprise secrets plugin to include static roles.
secrets/azure: Update plugin to v0.28.2+ent
secrets/gcp: Update plugin to v0.25.0
secrets/gcpkms: Update plugin to v0.25.0
secrets/keymgmt: Update plugin to v0.20.1+ent
secrets/kmip: Update plugin to v0.20.0
secrets/kubernetes: Update plugin to v0.14.0
secrets/kv: Update plugin to v0.27.0
secrets/ldap (enterprise): Static roles will be migrated from a plugin-managed queue to the Vault Enterprise Rotation Manager system. Static role migration progress can be checked and managed through a new static-migration endpoint. See the LDAP documentation for more details on this process.
secrets/mongodbatlas: Update plugin to v0.18.0
secrets/openldap: Update plugin to v0.19.1+ent
secrets/pki: sign-verbatim endpoints no longer ignore basic constraints extension in CSRs, using them in generated certificates if isCA=false or returning an error if isCA=true
secrets/ssh: RSA key sizes are now limited to a maximum size of 8192 bits addressing CVE-2026-39829
secrets/terraform: Update plugin to v0.15.0
secure-plugin-api: Update to v0.2.0
storage: Upgrade aerospike client library to v8.
ui/secrets: Secrets engines url paths renamed from '/secrets' to '/secrets-engines'
ui: Remove HCP Link status indicator following deprecation of HCP Link.
ui: Remove ability to bulk delete secrets engines from the list view.
FEATURES:
Transform FF1 Support (Enterprise): Add support for the NIST approved FF1 format preserving encryption (FPE) algorithm, and a new rewrap operation to assist transitioning
from FF3-1 to FF1.
PKI External CA (Enterprise): A new plugin that provides the ability to acquire PKI certificates from Public CA providers through the ACME protocol
AI Agent Support (Beta/Enterprise): Adds beta support for first-class AI agents. Adds an Agent Registry to register agents, and adds support for using Vault as an OAuth resource server for registered agent entities. When configured, allows OAuth 2.0 JWTs to be used to directly authorize requests to Vault, without needing a Vault token.
AI Agent Support (Enterprise): Vault's support for first-class AI agents is now Generally Available. Adds an Agent Registry to register agents, and adds support for using Vault as an OAuth resource server for registered agent entities. When configured, allows OAuth 2.0 JWTs to be used to directly authorize requests to Vault, without needing a Vault token.
Agent Registry UI (Enterprise): Adds a new Agentic Security section to the primary navigation with an Agent Registry page where operators can view, search, and manage registered AI agents, their associated Vault entities and aliases, assigned policies, and operational status.
Automatic DNS-01 Challenge Fulfillment for PKI External CA: Integrate with the following DNS providers for automatic DNS-01 challenge fulfillment: AWS Route53, Azure DNS, Google Cloud DNS, and BIND and other RFC2136-compliant servers.
Automatic TLS Certificate Reloading: TCP listeners accept a new tls_reload_interval option. When set, Vault periodically checks tls_cert_file and tls_key_file for changes and reloads the certificate automatically, so rotated certificates are picked up without restarting the node or sending SIGHUP.
Billing metrics dashboard: Create a new billing dashboard with responsive layout to display metric data.
Dark Mode (beta): Added dark mode support to the Vault UI. Users can now choose between light, dark, or system-preferred themes from the Appearance section in user preferences.
Health Check Manager: Adds a dedicated system to manage and monitor the health of Vault Enterprise plugins. This provides operators and platform engineers with an explicit mechanism to verify connectivity and authentication against external systems.
IBM PAO License Integration: Added IBM PAO license support, allowing usage of Vault Enterprise with an IBM PAO license key. A new configuration stanza license_entitlement is required in the Vault config to use an IBM license. For more details, see the License documentation.
KMIP Bring Your Own CA: Add new API to manage multiple CAs for client verification and make it possible to import external CAs.
LDAP Secrets Engine Enterprise Plugin: Add the new LDAP Secrets Engine Enterprise plugin. This enterprise version adds support for self-managed static roles and Rotation Manager support for automatic static role rotation. New plugin configurations can be set as "self managed", skipping the requirement for a bindpass field and allowing static roles to use their own password to rotate their credential. Automated static role credential rotation supports fine-grained scheduled rotations and retry policies through Vault Enterprise.
LDAP Secrets Engine Rotate on Read (Enterprise): Add rotate-on-read support for static roles in the LDAP secrets engine, triggering an immediate credential rotation on read, with a configurable cooldown period and per-role override.
Login MFA TOTP Self-Enrollment (Enterprise): Simplify creation of login MFA TOTP credentials for users, allowing them to self-enroll MFA TOTP using a QR code (TOTP secret) generated during login. The new functionality is configurable on the TOTP login MFA method configuration screen and via the enable_self_enrollment parameter in the API.
ML-DSA Support in PKI: Add support for post-quantum signatures with ML-DSA keys in the PKI secrets engine.
Namespace (Enterprise): Add operator_namespace_path to listener configuration to restrict HTTP access to a specific namespace subtree, enabling per-listener namespace isolation.
PKI BYOK CA Key Migration (enterprise): A new sudo-protected POST /pki/keys/:uuid/export endpoint wraps a CA private key with a caller-supplied public key using RSA-OAEP-SHA256, ECDH-ES, or ML-KEM. The destination Vault instance can import the blob via POST /pki/keys/import using wrapped_key and export_key_hmac. Export events are recorded as tamper-evident audit records keyed on the SPKI fingerprint of the CA key, which survive delete-and-reimport cycles and surface as warnings on issuer reads.
PKI PKCS#12 and JKS Support: Adds support for PKCS#12 (PFX) and Java keytool (JKS) certificate bundles to relevant PKI endpoints. Bundles are returned as base64-encoded, password-protected files.
PKI Secure Key Export (Enterprise): Add export key management CRUD endpoint (LIST/WRITE/READ/DELETE /pki/export) to support secure CA private key migration between PKI mounts.
Plugins (Enterprise): Allow overriding pinned version when creating and updating database engines
Plugins (Enterprise): Allow overriding pinned version when enabling and tuning auth and secrets backends
Rotation Policies: Add support for automated rotation parameters to rotation policies
SCIM 2.0 Identity Provisioning Beta (Beta/Enterprise): Adds beta support for Vault to act as a SCIM 2.0 server, allowing external management of Vault entities, aliases and groups.
SCIM Token Support (Enterprise): Add support for SCIM tokens via token_type=scim with per-client active token limits and max TTL ceilings.
SLH-DSA support for Hybrid sign/verify in Transit engine (Enterprise): Add support for SLH-DSA as the PQC component for Hybrid sign/verify operations. This is compatible with both ECDSA (p-256, P-384, P-521) and Ed25519.
Secrets Sync UI: Added Workload Identity Federation (WIF) support in the UI for AWS, Azure, and GCP sync destinations
Secrets Sync UI: Adds support to sync Database static roles
Secrets Sync UI: Implements AWS KMS key ID and regional KMS keys support
Secrets Sync UI: Implements GCP replica regions and encryption support
Secrets engines UI catalog revamp: Redesigned view of secrets engines catalog when enabling an engine, adding more engine descriptors & ability to search the catalog for the ideal engine to utilize.
Telemetry Consent Banner: Add a consent banner allowing users to accept or decline anonymous usage data collection to help improve Vault.
Template Integration for PublicPKICA: Vault Agent templates are now automatically re-rendered when a PKI external CA certificate is issued or renewed.
Terraform Code Generator: Adds TFVP code snippets to ACL policy surfaces (show, flyout and form), powered by a new reusable mapping engine for generating HCL from Vault API payloads.
Transit Crypto Agility: Allows customers to alter cryptographic primitives in transit engine. This adds new endpoints /transit/keys/:name/algorithm and /transit/keys/:name/import_version.
UI ACL Policies intro: Onboarding intro which provides feature context to users.
UI Authentication methods intro: Onboarding intro which provides feature context to users.
UI Namespace Wizard (Enterprise): Onboarding wizard which provides advice to users based on their intended usage and guides them through namespace creation.
UI Policy Generator (Enterprise): Adds policy generator flyout to KV V2 and PKI secrets engines prepopulated with relevant API requests for each page.
UI Secret engines intro: Onboarding intro which provides feature context to users.
UI TLS Certificate login: Add UI login support for the TLS certificate (cert) authentication.
UI: Hashi-Built External Plugin Support: Recognize and support Hashi-built plugins when run as external binaries
UI: Hashi-Built External Plugin Support: Support external plugin version updates via the GUI.
UI: Mount versioned external plugins: Adds ability to mount previously registered, external plugins and specify a version when enabling secrets engines.
UI: PKI External CA: Adds views to inspect ACME orders (active orders by role, lookup by order ID or certificate), ACME account, DNS provider, and role configurations, and retrieve cached certificates.
User Preference Settings: Added a User Preferences page (/vault/<cluster>/user-preferences) accessible from the account menu. Includes a Data & Privacy section with a telemetry consent toggle that persists per-browser in localStorage.
Vault Agent: ACME protocol support: Add support to natively support Public CA ACME workflows
Vault Client (Enterprise): Introduce vault-client, a smaller binary that includes Vault Agent, Vault Proxy, and the CLI commands for interacting with a Vault server, but not the server itself. It is available as zip bundles and Alpine container images.
oauth-resource-server: Added oauth_denylist.entries.gauge metric to monitor active OAuth token denylist entries.
secrets-sync (enterprise): Added support for the Database secrets engine as a sync source, allowing static-role credentials to be synced to external destinations.
oauth-resource-server: Added OAuth Protected Resource Metadata endpoint (RFC 9728) for publishing authorization_details types and enabling automated discovery by Authorization Servers via /.well-known/oauth-protected-resource
secrets-sync: implemented workload identity federation support for secrets sync flows.
secrets: Added ability to view secrets in YAML format
IMPROVEMENTS:
Secrets Engines UI improvement: Updated configuration views and added tune support for configurations across all compatible secrets engines.
Sidebar UI improvement: Add top navbar, update sidebar navigation structure, and update page headers.
Update github.com/dvsekhvalnov/jose2go to fix security vulnerability CVE-2025-63811.
activity (enterprise): Add a cumulative namespace client count API at sys/internal/counters/activity/cumulative. For each namespace in the response it returns the sum of its own client counts and that of all its child namespaces.
agent-registry (enterprise): Add a local flag to agent registrations. When local=true, registrations are not replicated to other performance replication clusters and are kept local to the current cluster.
agent-registry (enterprise): Removed the restriction that disallowed the use of 'deny' in ceiling policies, resulting in request errors.
agent/pkiexternalca: Replace go.uber.org/atomic with sync/atomic (stdlib) for atomic boolean operations in the pkiexternalca package.
api: Add start_month and end_month parameters to /sys/billing/overview endpoint to allow querying billing data for specific time ranges.
api: Add a SHA256 sum field to the json list response for external plugins.
api: Add migration_done_at_epoch to sys/seal-status response.
api: Added sudo-permissioned sys/reporting/scan endpoint which will output a set of files containing information about Vault state to the location specified by the reporting_scan_directory config item.
auth/aws: Added missing OpenAPI metadata for the aws auth endpoints
auth/aws: Migrate the AWS auth method, its public API client (api/auth/aws), and the shared login-data helper (internal/awsutil/v2) from AWS SDK for Go v1 to v2.
auth/cert: Support login via x-forwarded cert headers even with tls disabled on the vault listener.
auth/jwt (OAuth RS): Add EdDSA/Ed25519 support to the OAuth resource server JWT validation path. Ed25519 public keys can now be registered via public_keys and supported_algorithms = ["EdDSA"] is now accepted at configuration time and runtime.
auth/jwt: Add parameter constraint fields (allowed_parameters, denied_parameters, required_parameters) to vault:path_access RAR type schema and metadata for complete OAuth Resource Authorization Request support
auth/ldap: Require non-empty passwords on login command to prevent unauthenticated access to Vault.
auth/okta: Add missing OpenAPI path description for the /auth/{okta_mount_path}/verify/{nonce} path.
auth/okta: Added missing OpenAPI metadata for auth Okta plugin endpoints
auth/spiffe (enterprise): Add SPIFFE login cli handler.
auth/token: Add global denylist for revoking OAuth JWTs to prevent authorization of specific tokens across all namespaces.
auth/token: Add the revoke-oauth endpoint to revoke an external OAuth token by its issuer and unique ID.
auth/token: auth/token/revoke-accessor now supports revoking JWT tokens by accessor
ci (enterprise): Upload build stage duration metrics to Instana for CI observability.
command/agent: Migrate AWS client from aws-sdk-go v1 to aws-sdk-go-v2.
config/listener: logs warnings on invalid x-forwarded-for configurations.
consumption-billing: Add a new sys/billing/config endpoint to allow configuration of billing data retention (min 13 months, max 6 years).
consumption-billing: Add billing tracking for LDAP and OpenLDAP service account
library sets as part of both HWM role metrics and running-count product usage metric.
consumption-billing: Add billing tracking for OS Local Account static roles to support consumption-based billing metrics and high-water mark (HWM) tracking.
consumption-billing: Added consumption billing metrics for GCP KMS data protection operations.
consumption-billing: Added consumption billing metrics for OIDC tokens.
consumption-billing: Added consumption billing metrics for PKI External CA certificates.
consumption-billing: Added consumption billing metrics for SPIFFE JWT tokens.
consumption-billing: Adds a new sys/billing/overview endpoint that returns current and previous month consumption billing metrics. Accessible via API client method client.Sys().BillingOverview().
consumption-billing: Enabled sys/billing/overview endpoint in admin namespace.
consumption-billing: Float64 values returned by sys/billing/overview are now rounded to 4 decimal places.
consumption-billing: Increased billing data retention from 2 months to 37 months. The /sys/internal/billing/overview API endpoint now returns 37 months of historical consumption billing data by default.
consumption-billing: Mount attribution data is now stored for consumption billing metrics. The retention period can be configured via the new attribution_retention_months parameter on sys/billing/config (0–72 months, default 37). Setting to 0 disables attribution storage and immediately wipes all existing attribution data.
consumption-billing: The /sys/internal/billing/overview API endpoint now always returns all metric types in the response, even when their values are zero. This ensures consistent response structure for easier client-side parsing.
core (enterprise): Make deadlock detection in sealwrap configurable by adding "sealwrap" to existing configuration detect_deadlocks.
core (enterprise): Sanitized config now shows kms_library config.
core (enterprise): Add OAuth resource server authorization_details type discovery endpoints and align vault:path_access claim matching semantics with path/capabilities evaluation; discovery endpoints are unauthenticated.
core (enterprise): Add disallow_env_vars in PKCS#11 to allow per key configuration for RSA encryption algorithm.
core (enterprise): Add sys/config/ui/checklist-state endpoint to persist and retrieve onboarding checklist progress.
core (enterprise): Add an endpoint at sys/config/oauth-resource-server/id/:config_id to read oauth resource server profiles by config_id
core (enterprise): Add common_criteria_mode feature_flags setting which limits listener TLS cipher suites.
core (enterprise): Added a new telemetry metric vault.core.license.termination_time_epoch.
core (enterprise): Make OAuth resource server JWT typ validation more permissive for tokens from IdPs such as Okta by allowing a missing typ header, while restricting present typ values to at+jwt, application/at+jwt, and JWT.
core (enterprise): allow secretmounts' seal wrap configuration to be changed via auth and/or mount tune instead of only at mount creation.
core (enterprise): enable rotation manager to send rotation information required by plugin backends during registration and rotation operations. This allows plugin backends to have the necessary context for managing their rotation state effectively.
core (enterprise): enable rotation manager to use configurable retry policies to limit the retry behavior for rotation entries and include an orphaning mechanism to handle entries that exceed the maximum retry attempts.
core (enterprise): improve rotation manager error handling by implementing a backoff when re-queueing failed rotations
core (enterprise): Ameriolate sealwrap lock contention for core paths.
core/acl: Adds a global deny_slash_in_templated_path configuration option to reject the presence of slashes in rendered identity templates in policies, defaulting to false.
core/census: Add vault.secret.engine.transform.role.count product usage metric reporting the number of Transform secret engine roles.
core/census: Add product usage metrics vault.auth.method.cert.role.count, vault.auth.method.cert.crl.count, vault.auth.method.spiffe.role.count, and vault.auth.method.scep.role.count reporting the number of Cert auth roles and CRLs, SPIFFE auth roles, and SCEP auth roles across all namespaces and mounts, and vault.auth.method.spiffe_enabled reporting whether the SPIFFE auth method is enabled.
core/census: Add product usage metrics reporting the number of Transform secret engine transformations, templates, alphabets, and stores, and KMIP secret engine scopes, scope roles, and CAs.
core/identity: Add two new fields to the alias API, external_id and issuer. These fields do not inherently do anything meaningful, and are part of a future feature.
core/identity: Adds a global deny_slash_in_templated_path configuration option to reject the presence of slashes in rendered identity templates in policies, defaulting to false.
core/managed-keys (enterprise): Allow GCP managed keys to leverage workload identity federation credentials
core/managed-keys/PKCS#11 (enterprise): Add PKCS#11 backend parameter rsa_oaep_hash to use for RSA-OAEP encryption with CKM_RSA_PKCS_OAEP mechanism.
core/managed-keys/PKCS#11 (enterprise): Providing a non-empty value for one field while the other is already saved is rejected. To switch addressing modes, you must explicitly clear the old field by sending it as an empty string ("") in the same request alongside the new value.
core/managed-keys/PKCS#11 (enterprise): slot and token_label are now strictly enforced as mutually exclusive identifiers for an HSM token
core/metrics: Reading and listing from a snapshot are now tracked via the vault.route.read-snapshot.{mount_point} and vault.route.list-snapshot.{mount_point} metrics.
core/oauth-resource-server (enterprise): Read and list responses for sys/config/oauth-resource-server now include a mount_accessor field containing the pre-assembled synthetic accessor string (oauth-resource-server_<namespace_id>_<config_id>). This is the accessor reported for profile-backed aliases in identity and audit output, and the value used to select those aliases in templated policies.
core/oauth-resource-server (enterprise): Support setting an alternate claim name in an OAuth Resource Configuration specifying where to read authorization details in a presented JWT. New option "authorization_details_claim" defaults to "authorization_details".
core/oauth-resource-server (enterprise): The list response for sys/config/oauth-resource-server now includes a key_info map keyed by profile name, each entry carrying config_id and mount_accessor. Listed profile names are now sorted, and profiles whose details cannot be read are reported in a response warning.
core/oauth-resource-server: Support data locality for OAuth Resource Server configuration profiles (non-replicated profiles).
core/seal (enterprise): Make it possible for new nodes to join a cluster configured with Seal High Availability.
core/seal (enterprise): Update Oracle Cloud library to enable seal integration with newer regions.
core/seal: Enhance sys/seal-backend-status to provide more information about seal backends.
core: Add a ui_settings configuration stanza with a ui_telemetry option, surfaced to the UI via the sys/internal/ui/settings endpoint, that gates anonymous UI usage telemetry.
core: Automatically write a goroutine dump to a temp directory on shutdown (SIGTERM/SIGINT). The output directory can be overridden with VAULT_STACKTRACE_FILE_PATH, and the dump can be suppressed with the config field disable_goroutine_trace_dump.
core: Enforce OAuth authorization_details vault:path_access constraints with strict path/capabilities and parameter-level controls.
core: Improve goroutine termination during preseal.
core: check rotation manager queue every 5 seconds instead of 10 seconds to improve responsiveness
dockerfile: container will now run as vault user by default
events (enterprise): Add event notifications support for lease events.
events (enterprise): Forward event notifications from primary to secondary clusters
events: Add VAULT_EVENT_NOTIFICATIONS_BOUNDED_QUEUE_SIZE environment variable to configure bounded event queues for event notification subscribers. Set to a positive integer (e.g., 16) to enable buffered channels of that size (maximum 1000). This prevents resource exhaustion in deployments with high subscriber counts, but comes at the cost of the potential for subscribers to miss events. Defaults to 0 (unbuffered) for backward compatibility.
events/sqs: Migrate SQS event subscription plugin from aws-sdk-go v1 to aws-sdk-go-v2.
go: update to golang/x/crypto to v0.45.0 to resolve GHSA-f6x5-jh6r-wrfv, GHSA-j5w8-q4qc-rx2x, GO-2025-4134 and GO-2025-4135.
identity/entity-alias: Added profile_name and config_id fields as shortcuts to resolve an OAuth Resource Server profile when creating entity aliases, without requiring a mount_accessor. Resolving a profile also binds the alias to that profile's issuer, which OAuth Resource Server authentication requires. The fields are mutually exclusive with each other and with mount_accessor.
identity/scim (enterprise): Add POST identity/scim/client/<client-name>/link-entity endpoint to re-establish SCIM ownership over an unmanaged entity, restoring managed aliases and group memberships.
identity/scim (enterprise): Add POST identity/scim/client/<client-name>/link-group and POST identity/scim/client/<client-name>/unlink-group admin endpoints. link-group transfers ownership of an existing unmanaged Vault identity group to the named SCIM client; all current group members must already be owned by that client. unlink-group removes SCIM ownership from a group the client currently owns, returning it to unmanaged status.
identity/scim (enterprise): Add POST identity/scim/client/<client-name>/unlink-entity endpoint to remove the SCIM ownership link from an entity without deleting it.
identity/scim (enterprise): Add allow_user_adoption field to SCIM client configuration. When set to true, a POST /Users request whose userName matches an existing login alias will adopt the pre-existing entity rather than returning a conflict. Defaults to false.
identity/scim (enterprise): Add support for attributes and excludedAttributes query parameters on SCIM User and Group endpoints, allowing callers to request a subset or exclusion of attributes in responses per RFC 7644.
identity/scim (enterprise): Added filtering support to the GET /scim/v2/Users and GET /scim/v2/Groups endpoints per RFC 7644. Supported filters: userName eq, externalId eq, active eq, and meta.lastModified gt/ge/lt/le for Users; displayName eq and meta.lastModified gt/ge/lt/le for Groups. Unsupported filter expressions return HTTP 400. ServiceProviderConfig now advertises filter.supported: true.
identity/scim (enterprise): Fix Group PATCH to support filtered member paths of the form members[value eq "uuid"] for add and replace operations, matching the path format already supported for remove. This resolves an Okta error ("unsupported path") during Group Push membership updates. Group ownership mismatches now return 403 Forbidden (previously 404 Not Found); attempting to add/replace members owned by a different SCIM client now returns 403 (previously 400 with a not found-style detail).
identity/scim (enterprise): Improve SCIM User and Group listing endpoint performance by using prefix sort instead of a separate sort pass.
identity/scim (enterprise): Renamed the unlink_aliases consent parameter to unlink_secondary_aliases and separated the response payload into unlinked_main_alias_id and unlinked_secondary_alias_ids.
identity/scim (enterprise): The 2.1 User extension now supports a client-managed aliases attribute. SCIM clients can push an array of {mount_accessor, name} entries on POST, PUT, and PATCH /Users to create, rename, or remove secondary aliases on an entity beyond the primary alias controlled by alias_mount_accessor.
identity/scim (enterprise): Update PATCH operations on scim/v2/Users to allow multiple modifications in the same patch call, support for patch operations on user metadata and name in addition to active status, and allow specifying path value in patch operations
identity/scim: New SCIM extensions for Users and Groups are supported, but mutually exclusive with User metadata extension.
identity/scim: POST /Users for a client with alias_mount_accessor now adopts a pre-existing entity when the userName matches an existing login alias on the target mount, instead of failing with a conflict.
identity/scim: Unmanaged groups (no SCIM owner) are now visible to all SCIM clients via GET /Groups and GET /Groups/. Groups owned by a different client remain hidden (403 on direct read). For unmanaged groups, the members array is filtered on read to only the members owned by the requesting client.
identity/scim: externalId is now optional on POST /Users and is no longer required to be unique within a namespace. Multiple users may share the same externalId value.
identity/scim: permit adoption of unmanaged Vault groups only on PUT or PATCH SCIM requests.
identity: Include entity status and entity/alias timestamp details in entity list key_info responses.
jwt/oauth-resource-server: Profile resolution now walks the namespace ancestor chain, allowing a JWT whose OAuth Resource Server Configuration Profile is registered in a parent namespace to authenticate requests targeting resources in child namespaces.
kmip (enterprise): Add experimental API to execute KMIP requests.
license utilization reporting (enterprise): Add metrics for the number of issued PKI certificates.
license utilization reporting (enterprise): Utilization reports now include new license metadata fields issuer, edition, add_ons, license_start_time, license_expiration_time, and license_termination_time.
license utilization reporting: Added consumption billing metrics.
oauth-resource-server: Add support for fine-grained policy control options (parameter constraints) in Rich Authorization Requests (RAR), including allowed_parameters, denied_parameters, and required_parameters inside authorization_details.
oauth-resource-server: Add support for identity template expressions (e.g. {{identity.entity.id}}) in Rich Authorization Requests (RAR).
oauth-resource-server: Improved error body returned when permission is denied by ceiling policies to indicate that ceiling policies were what denied the request (CEILING_POLICY_DENIED).
pki: Reject obviously unsafe validation targets during ACME HTTP-01 and TLS-ALPN-01 challenge verification
policies: add warning about list comparison when using allowed_parameters or denied_parameters
product usage reporting (enterprise): Add vault.secure_hub_connected Census product usage metric to report whether a cluster is connected to the Secure Hub.
rotation: Ensure rotations for shared paths only execute on the Primary cluster's active node. Ensure rotations for local paths execute on the cluster-local active node.
scim: The SCIM Group PATCH handler now supports the path field in the form members[value eq "id"] on remove operations.
scim: User resources now include a read-only groups field listing the direct group memberships managed by the requesting SCIM client, per RFC 7643.
sdk/helper/keysutil: The lock manager's GetPolicy function now always returns a locked Policy, even when caching is enabled. The PolicyRequest struct has a new field to indicate whether the caller requires a write lock on the policy.
sdk/rotation: Prevent rotation attempts on read-only storage
sdk: Add NewTestDockerCluster support for running external plugins within the same container as the server. Also add support for those plugins to expose their own listeners, as KMIP does.
sdk: Add alias_metadata to tokenutil fields that auth method roles use.
sdk: Expand support for docker test cluster options like seals, kms libraries, and entropy augmentation. DockerClusterNode.UpdateConfig now takes a full set of cluster options instead of just node config.
sdk: add WIF and rotation helpers for checking if params were updated to allow the consumer to know when changes need to be persisted to storage
secret-sync (enterprise): Added telemetry counters for reconciliation loop operations, including the number of corrections detected, retry attempts, and operation outcomes (success or failure with internal/external cause labels).
secret-sync (enterprise): Added telemetry counters for sync/unsync operations with status breakdown by destination type, and exposed operation counters in the destinations list API response.
secret-sync: add parallelization support to sync and unsync operations for secret-key granularity associations
secrets import: Add support for allowed_ipv4_cidrs in source_aws and source_azure configuration blocks to allow connections to explicitly permitted private IPv4 ranges.
secrets-pki (enterprise): Add response data in a parsed format to the audit log for enrollment protocols.
secrets-sync (enterprise): Added support for a boolean force_delete flag (default: false). When set to true, this flag allows deletion of a destination even if its associations cannot be unsynced. This option should be used only as a last-resort deletion mechanism, as any secrets already synced to the external provider will remain orphaned and require manual cleanup.
secrets-sync (enterprise): Improved the user experience during mount lifecycle changes by triggering immediate unsyncing of external secrets when a secrets engine mount is deleted or disabled. By moving this logic from the background reconciliation loop to a direct callback, the system prevents perceived "leaks" and ensures external secret resources are cleaned up synchronously with the Vault unmount.
secrets-sync: Adds support for customer-controlled (CSP Managed) encryption in secrets sync flows for AWS destination.
secrets/aws: Added missing OpenAPI metadata for the aws secret engine endpoints
secrets/aws: Migrate AWS client from aws-sdk-go v1 to aws-sdk-go-v2.
secrets/database: Add root rotation support for Snowflake database secrets engines using key-pair credentials.
secrets/keymgmt (enterprise): Add support for multi-region AWS KMS keys.
secrets/kmip (enterprise): Obey configured best_effort_wal_wait_duration when forwarding kmip requests.
secrets/kv (enterprise): Support reading and recovering KVv2 secrets from a loaded snapshot, including in-place recover and copy-from-path within the same mount and namespace.
secrets/ldap: Users can now fully manage and tune the LDAP secrets engine. This includes the ability to view, edit, and configure the LDAP engine.
secrets/pki (enterprise): Allow SCEP to use an issuer that is backed by an RSA based PKCS#11 managed key
secrets/pki (enterprise): Return the POSTPKIOperation capability within SCEP GetCACaps endpoint for better legacy client support.
secrets/pki (enterprise): Validate entire chain in common criteria mode; add field to enable time checks on validation
secrets/pki (enterprise): When the common_criteria_mode feature flag is enabled, NotBefore will always be treated as zero.
secrets/pki (enterprise): When the common_criteria_mode feature flag is enabled, enforce a minimum set of key usages for each ext key usage set based on RFC 5280 Section 4.2.1.12 during PKI role updates.
secrets/pki: Add ACME configuration fields challenge_permitted_ip_ranges and challenge_excluded_ip_ranges configuration to control which IP addresses are allowed or disallowed for challenge validation.
secrets/pki: Add Freshest CRL extension (Delta CRL Di - Oct 8, 2026
- Date parsed from source:Oct 8, 2026
- First seen by Releasebot:Oct 16, 2026
- Modified by Releasebot:Nov 13, 2026
v2.1.2
Vault strengthens ACL, policy, and plugin security, tightens ACME certificate validation, adds SPIFFE login CLI support and extra PKI subject-name OIDs, and fixes AppRole CIDR validation and child-namespace client-count reporting.
October 07, 2026
BREAKING CHANGES:
- pki: ACME finalization with the default sign-verbatim directory policy now rejects CSRs that contain URI SANs, email SANs, or Other SANs. ACME challenges only verify DNS names and IP addresses; those SAN types are never validated and must not appear in issued certificates. Operators who require the previous behaviour can set default_directory_policy = "sign-verbatim-unsafe" in config/acme, accepting that the resulting certificates may contain unverified identity claims.
SECURITY:
- core (enterprise): Prevent policy-name canonicalization bypasses in ACL parameter restrictions.
- core/plugin: Fix plugin catalog entries restored from a raft snapshot, written through sys/raw, or replicated being able to run a binary outside plugin_directory.
- core/policy: Harden request-time ACL construction to ignore malformed legacy policy references containing path-navigation segments (. or ..) so traversal-style names are never resolved or applied.
- core: Fixed a bypass of exact-deny ACL policies where case-variant AppRole, AWS, Azure, GCP, Kubernetes, SCEP, or TPM role names, GitHub team or user policy mapping keys, certificate or CRL names, ACL/RGP/EGP policy names, or userpass usernames could evade the deny and be resolved by the backend to the same protected resource. Okta group names, LDAP and RADIUS names on mounts left in their default case-insensitive configuration, and Enterprise SCIM client names (identity/scim/client/<name>, where a case-variant write overwrites the existing client) are not covered by this fix and remain subject to the same bypass; avoid combining a wildcard allow with an exact deny on those mounts and paths.
CHANGES:
- core/plugin: Plugin catalog entries are now checked against plugin_directory whenever they are used, not only at registration. An entry whose command resolves outside the directory, including through a symlink, is refused with plugin command is outside of configured plugin directory, and mounts that use it are skipped at startup while keeping their data. Such plugins must be registered again with their binary inside plugin_directory.
- core/policy: Vault now validates policy names with segment-aware checks. Empty names and names containing . or .. path segments are rejected for new policy writes and assignments, while names containing / and \ remain supported. During request-time ACL construction, legacy traversal-style policy references are not applied (treated as invalid and unresolved), which can reduce effective token permissions. Operators should audit and rename affected policies before upgrading.
- core: ACL and Sentinel EGP rule paths targeting a specific AppRole, AWS, Azure, GCP, Kubernetes, SCEP, or TPM role, GitHub team or user policy mapping key, certificate or CRL name, ACL/RGP/EGP policy name, or userpass username are now matched against the lowercased resource name, since these backends resolve those names case-insensitively. A rule written with a mixed-case resource name (for example auth/approle/role/MyRole) no longer matches requests for that resource and must be rewritten using the lowercase name (auth/approle/role/myrole). The lowercased form is also what Sentinel RGP and EGP policies observe as request.path, so policy rules that compare that value against a mixed-case path (for example request.path is "auth/approle/role/MyRole") must be updated as well. External auth and secret plugins are not affected by this normalization and continue to receive requests with their original casing. Existing deny rules using mixed-case resource names will fail open (become allow-all) after upgrade until rewritten with lowercase names.
IMPROVEMENTS:
- auth/spiffe (enterprise): Add SPIFFE login cli handler.
- secrets/pki: Add extra_subject_names_oids field to roles to allow specifying additional OID subject name components.
BUG FIXES:
- auth/approle: Fix token_bound_cidrs validation when using /128 blocks for role and secret ID
- ui: Fix regression where the client count billing configuration request omitted the root-namespace header, causing 404s on Monitoring > Client Count when viewed from a child namespace
- Oct 7, 2026
- Date parsed from source:Oct 7, 2026
- First seen by Releasebot:Oct 23, 2026
- Modified by Releasebot:Nov 11, 2026
v1.17.0-rc1
Terraform releases 1.17.0-rc1 with generally available policy support, variables and locals in provider requirements, and a minimal-refresh planning option. It also improves testing and diagnostics while fixing policy query, cleanup ordering, and numeric function issues.
1.17.0-rc1 (October 07, 2026)
NEW FEATURES:
- Terraform now supports variables and locals in provider requirements (#39153)
- A new -minimal-refresh planning option has been added, which will only refresh resources that have proposed changes. (#35290)
- policy: Terraform Policy is now generally available. The -policies flag for plan, apply, and query no longer requires an experimental build or the -allow-experimental-features flag. Query policies evaluate resources discovered by list blocks and report human-readable or JSON results. See https://developer.hashicorp.com/terraform/policy for more information. (#38970)
ENHANCEMENTS:
- command/init: Enrich log messages with provider versions (#38918)
- test: Add mock_provider support for ephemeral resources (#38928)
- command/login: display warning after successful login if user is subject to an organization's TTL policy
BUG FIXES:
- funcs: pow and log no longer panic when result is not a number (#38912)
- ephemeral: Terraform will now use and display diagnostics raised when renewing an ephemeral resource. This may cause warnings to appear that previously were lost. We expect that any error diagnostics that were previously lost would have caused confusing downstream errors, so we do not anticipate this change to be breaking. (#38989)
- test: Deterministic dependency ordering in cleanup graph (#38247)
- query: report Unknown and N/A results for policy evaluations of discovered resources (#39058)
- query: terraform query -policies now rejects a path that is not a directory, instead of passing it on to the policy engine (#39238)
NOTES:
- version: JSON output now includes a new format_version field, which will enable safer future changes of the command's JSON output format. It is assumed existing tooling ignores unknown fields and therefore this change should not be breaking in itself but we advice consumers to pay attention to format_version in future releases and/or use latest version of hashicorp/terraform-json & hashicorp/terraform-exec which does. (#38930)
Previous Releases
For information on prior major and minor releases, refer to their changelogs:
- v1.16
- v1.15
- v1.14
- v1.13
- v1.12
- v1.11
- v1.10
- v1.9
- v1.8
- v1.7
- v1.6
- v1.5
- v1.4
- v1.3
- v1.2
- v1.1
- v1.0
- v0.15
- v0.14
- v0.13
- v0.12
- v0.11 and earlier
- Oct 2, 2026
- Date parsed from source:Oct 2, 2026
- First seen by Releasebot:Oct 2, 2026
v1.16.5
Terraform 1.16.5 fixes crashes and resource identity issues in instance state and delete handling.
1.16.5 (September 30, 2026)
BUG FIXES:
- Fixed a crash that happens when a tainted instance state is seen without a valid status (#39287)
- resource-identity: fixed an issue where resource identity could be nil during delete (#39285)
- Sep 23, 2026
- Date parsed from source:Sep 23, 2026
- First seen by Releasebot:Sep 23, 2026
v1.16.4
Terraform fixes policy evaluation rendering and stack deferral errors in 1.16.4.
1.16.4 (September 23, 2026)
BUG FIXES:
- Fixed an issue where Terraform fails when rendering policy evaluation outcomes for older versions of Terraform Enterprise (#39095)
- stacks: Fix invalid deferred error triggered by provider returning a deferral when a resource also has an unknown count/for_each. (#39237)
- Sep 17, 2026
- Date parsed from source:Sep 17, 2026
- First seen by Releasebot:Sep 25, 2026
v2.1.1
Vault releases 2.1.1 with critical security updates, Okta JWT group fetching, tighter raft retry-join limits, secrets import CIDR exemptions, PKI revocation reason support, and fixes across recovery, auth, sync, plugins, and UI.
2.1.1
September 16, 2026
SECURITY
core: Update github.com/apache/thrift to v0.24.0 to fix security vulnerability GHSA-8wv5-x4w7-5gww.
core: Update golang.org/x/crypto to v0.56.0 to fix security vulnerabilities GO-2026-6354 and GO-2026-6355.
core: Update google.golang.org/grpc to v1.83.2 to fix security vulnerability GHSA-2v4p-qf9q-27wj.
CHANGES
auth/jwt: Added Okta provider with group fetching from Admin API when fetch_groups=true and truncation is detected.
auth/jwt: Update plugin to v0.26.4
core/raft: Limited concurrent retry-join workers to 20. Any further retry-join attempts while 20 are in progress will result in an error (too many concurrent raft retry joins in progress).
core: Bump Go version to 1.26.8
IMPROVEMENTS
secrets import: Add allowed_ipv4_cidrs to source_aws and source_azure Secrets Import blocks to allow private CIDR exemptions for SSRF-safe connectivity.
secrets/pki: add an additional field to include an RFC 5280 revocation reason for (/pki/revoke) and (/pki/revoke-with-key).
ui: Bump dompurify to 3.4.15 to address SECVULN advisories
BUG FIXES
Secrets Recovery (enterprise): Fixing Vault panic in cli when running vault recover without a path.
auth/jwt: Fixed incorrect HTTP status codes returned during agent ceiling policy evaluation.
auth/token: Fixed a bug where auth/token/lookup and auth/token/lookup-self returned 403 for JWT tokens in a non-root namespace.
consumption-billing: Fix OIDC identity token billing units being computed incorrectly across periodic flush cycles. The billing scalar now applies per-token duration adjustment, so the reported scalar and the per-mount attribution breakdown are always consistent.
core/activitylog (enterprise): Fix a panic in CensusReport ACL policy metrics collection by safely handling transient missing policies and nil policy path/permission data while policies are changing.
core/mounts: Fixed vault secrets move (and vault auth move) incorrectly placing a mount in the root namespace when the destination path has a leading slash.
oauth-resource-server (enterprise): Fix issue where RAR enforcement was skipped when the token's iss claim had cosmetic differences (e.g. different casing or trailing slash) compared to the issuer stored in the resource server profile.
plugins: Fix issue with vault plugin reload -mounts command when run in the root namespace
secrets-sync (enterprise): Fix LIST /v1/sys/sync/associations intermittently returning zero associations/secrets by forwarding the request to the active node instead of allowing it to be served locally by a performance standby or performance secondary.
secrets/pki (enterprise): Fix panic in CMPv2 sentinel field parsing when cert request messages are empty.
secrets/pki (enterprise): Fix unified CRL not being rebuilt after the background transfer copies locally-revoked certificates into unified storage.
ui: Fix agent registry ceiling policies not displaying due to incorrect property name
ui: Fix total secrets count binding on secrets sync overview page to match the API response key.
ui: Resolve the flickering on the login page when a trailing slash is added to the namespace in the field.
Original source - Sep 16, 2026
- Date parsed from source:Sep 16, 2026
- First seen by Releasebot:Sep 23, 2026
v1.16.3
Terraform 1.16.3 fixes destroy handling, mark validation, import provider resolution, and other bugs.
1.16.3 (September 16, 2026)
BUG FIXES:
- Fix handling of destroy=false around create_before_destroy instances (#39169)
- Fix function result comparison when there are multiple marks (#39170)
- Filter logic for marks could cause values with multiple marks to erroneously fail validations (#39171)
- Fix issue with import provider resolution (#39185)
- Sep 9, 2026
- Date parsed from source:Sep 9, 2026
- First seen by Releasebot:Sep 9, 2026
v1.16.2
Terraform fixes a panic in module installation when encountering invalid module calls in 1.16.2.
1.16.2 (September 9, 2026)
BUG FIXES:
- Fix panic in module installation when encoutering invalid module calls (#39129)
Curated by the Releasebot team
Releasebot is an aggregator of official release notes from hundreds of software vendors and thousands of sources.
Our editorial process involves the manual review and audit of release notes procured with the help of automated systems.