Update dependency hashicorp/vault to v2 - #39
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/hashicorp-vault-2.x
branch
2 times, most recently
from
May 19, 2026 23:14
0805d72 to
d68f795
Compare
renovate
Bot
force-pushed
the
renovate/hashicorp-vault-2.x
branch
from
June 5, 2026 19:43
d68f795 to
339ffdc
Compare
renovate
Bot
force-pushed
the
renovate/hashicorp-vault-2.x
branch
from
June 17, 2026 22:59
339ffdc to
998e4a1
Compare
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovate
Bot
force-pushed
the
renovate/hashicorp-vault-2.x
branch
from
August 4, 2026 19:47
998e4a1 to
d43eb20
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.21.4→v2.0.4Release Notes
hashicorp/vault (hashicorp/vault)
v2.0.4Compare Source
2.0.4
August 04, 2026
BREAKING CHANGES:
images: gnupg, openssl, procps.
SECURITY:
denied_parametersconstraint on thepoliciesrequest field could be bypassed by submitting a mixed-case policy name (e.g. "Super-Admin" instead of "super-admin"). Vault now normalizes thepoliciesparameter to lowercase before evaluatingallowed_parameters/denied_parametersconstraints.identity/entity/mergeendpoint 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.CHANGES:
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.
FEATURES:
IMPROVEMENTS:
sys/config/oauth-resource-server/id/:config_idto read oauth resource server profiles byconfig_idtypvalidation more permissive for tokens from IdPs such as Okta by allowing a missingtypheader, while restricting presenttypvalues toat+jwt,application/at+jwt, andJWT.deny_slash_in_templated_pathconfiguration option to reject the presence of slashes in rendered identity templates in policies, defaulting tofalse.deny_slash_in_templated_pathconfiguration option to reject the presence of slashes in rendered identity templates in policies, defaulting tofalse.VAULT_EVENT_NOTIFICATIONS_BOUNDED_QUEUE_SIZEenvironment 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.GET /scim/v2/UsersandGET /scim/v2/Groupsendpoints per RFC 7644. Supported filters:userName eq,externalId eq,active eq, andmeta.lastModified gt/ge/lt/lefor Users;displayName eqandmeta.lastModified gt/ge/lt/lefor Groups. Unsupported filter expressions return HTTP 400.ServiceProviderConfignow advertisesfilter.supported: true.allowed_parameters,denied_parameters, andrequired_parametersinsideauthorization_details.{{identity.entity.id}}) in Rich Authorization Requests (RAR).groupsfield listing the direct group memberships managed by the requesting SCIM client, per RFC 7643.tmpfrom 0.2.6 to 0.2.7.wsfrom 8.20.1 to 8.21.0.BUG FIXES:
sys/storage/raft/snapshot-loador read/delete requests tosys/storage/raft/snapshot-load/{id}. If possible, handle these requests on the performance standby, otherwise forward the requests to the active node.sys/billing/overviewto return a 500 error with "lz4: bad magic number". The storage encoding now uses plain decimal strings consistent with other billing metrics, avoiding misidentification as lz4-compressed data.to use dedicated count endpoints (role-count, static-role-count) instead of LIST-based counting, which was undercounting roles.
Previously, the redirect dropped parameters such as
?list=true, potentially changing the result of the request.authorization_detailsarray like an absent claim when authorization details are optional. Previously, tokens containing an empty array were rejected withRAR_NO_MATCHinstead of continuing through normal identity and policy authorization.tls_disablewhen displaying TLS status in the Cluster Configuration widget.v2.0.3Compare Source
SECURITY:
CHANGES:
path "kv/*" { deny }could be bypassed forLIST kv/private/if a broader allowpath "kv/*"also existed. Policies relying on the previous (incorrect) behavior may now be denied././,/../, or//) to a cleaned path, instead of rejecting these requestsFEATURES:
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.
IMPROVEMENTS:
sys/billing/configendpoint to allow configuration of billing data retention (min 13 months, max 6 years).pathvalue in patch operationsenabled. The PolicyRequest struct has a new field to indicate whether the caller requires a write lock on the policy.
BUG FIXES:
performance_multipliervalues less than or equal to zerov2.0.2Compare Source
BREAKING CHANGES:
cap_ipc_lockcapability onvaultat build time to allow running Vault in common container runtimes. Vault in containers will no longer be able to callmlock()to lock memory. Operators should setdisable_mlock = truein Vault's configuration. Runtime operators are advised to disable swapping to guarantee data safety.CHANGES:
BUG FIXES:
v2.0.1Compare Source
BREAKING CHANGES:
SECURITY:
CHANGES:
FEATURES:
IMPROVEMENTS:
BUG FIXES:
v2.0.0Compare Source
BREAKING CHANGES:
SECURITY:
cloudflare/circlto v1.6.3 to resolve CVE-2026-1229filippo.io/edwards25519to v1.1.1 to resolve GO-2026-4503max_token_header_sizelistener option (default 8 KB) to bound the size of authentication token headers (X-Vault-TokenandAuthorization: Bearer), preventing a potential denial-of-service attack via oversized header contents. The stdlib-levelMaxHeaderBytesbackstop is also now set on the HTTP server. Setmax_token_header_size = -1to disable the limit.cloudflare/circlto v1.6.3 to resolve CVE-2026-1229go.opentelemetry.io/otel/sdkto v1.40.0 to resolve GO-2026-4394CHANGES:
supplemental_audit_datacan 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. Theaudit-non-hmac-request-keysandaudit-non-hmac-response-keysapply to keys withinsupplemental_audit_datato remove the HMAC of the field values if so desired.path//to/resource)vault operator utilizationhave a changed format. Notably they contain an array ofsnapshot_recordsinstead ofsnapshots. Thedecoded_snapshotfield in each record contains the human-readable data that was previously in thesnapshotsarray.FEATURES:
license_entitlementis required in the Vault config to use an IBM license. For more details, see the License documentation.enable_self_enrollmentparameter in the API.IMPROVEMENTS:
sys/reporting/scanendpoint which will output a set of files containing information about Vault state to the location specified by thereporting_scan_directoryconfig item.sys/billing/overviewendpoint that returns current and previous month consumption billing metrics. Accessible via API client methodclient.Sys().BillingOverview().vault.core.license.termination_time_epoch.vault.route.read-snapshot.{mount_point}andvault.route.list-snapshot.{mount_point}metrics.issuer,edition,add_ons,license_start_time,license_expiration_time, andlicense_termination_time.supplemental_audit_datasection of audit log response entries. Details such as issuer_id, next_update, ocsp_status, serial_number, revoked_at will appear as hmac values by default unless added to the mount'saudit-non-hmac-response-keysset of keys.server_flag,client_flag,code_signing_flag, andemail_protection_flagparameters for creating/updating a role.BUG FIXES:
alias_metadatanow populates alias custom metadata field instead of alias metadata.alias_metadatanow populates alias custom metadata field instead of alias metadata.alias_metadatanow populates alias custom metadata field instead of alias metadata.alias_metadatanow populates alias custom metadata field instead of alias metadata.alias_metadatanow populates alias custom metadata field instead of alias metadata.alias_metadatanow populates alias custom metadata field instead of alias metadata.alias_metadatanow populates alias custom metadata field instead of alias metadata.alias_metadatanow populates alias custom metadata field instead of alias metadata.alias_metadatanow populates alias custom metadata field instead of alias metadata.log_requests_levelconfiguration was not respected on a SIGHUP reload when set to "off" or removed from the config file.key_usageextension so details accurately reflect certificate values.basic_constraints_valid_for_non_cais correctly set.?with=<path>query param correctly displays only the specified mount when multiple mounts of the same auth type are configured withlisting_visibility="unauth"Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.