Skip to content

go: resolve GHSA-7j59-v9qr-6fq9 by upgrading github.com/microsoft/kiota-http-go to v1.5.5 on release/vault-1.19#293

Merged
kporter101 merged 1 commit into
release/vault-1.19.xfrom
kp/vault-44841-19
May 14, 2026
Merged

go: resolve GHSA-7j59-v9qr-6fq9 by upgrading github.com/microsoft/kiota-http-go to v1.5.5 on release/vault-1.19#293
kporter101 merged 1 commit into
release/vault-1.19.xfrom
kp/vault-44841-19

Conversation

@kporter101
Copy link
Copy Markdown
Contributor

@kporter101 kporter101 commented May 12, 2026

Overview

VAULT-44841

Design of Change

  • Bumped kiota-http-go to the next version which resolves the vuln (1.5.5)
  • Ran go mod tidy

Related Issues/Pull Requests

[ ] Issue #1234
[ ] PR #1234

Contributor Checklist

[ ] Add relevant docs to upstream Vault repository, or sufficient reasoning why docs won’t be added yet
My Docs PR Link
Example
[ ] Add output for any tests not ran in CI to the PR description (eg, acceptance tests)
[ ] Backwards compatible

PCI review checklist

  • I have documented a clear reason for, and description of, the change I am making.

  • If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.

  • If applicable, I've documented the impact of any changes to security controls.

    Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.

@kporter101 kporter101 requested a review from a team as a code owner May 12, 2026 16:19
@kporter101 kporter101 merged commit bd5af5b into release/vault-1.19.x May 14, 2026
4 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants