Skip to content

Backport of chore: Suppress CVE-2026-41989 into release/0.21.x - #6773

Closed
hc-github-team-secure-boundary wants to merge 1 commit into
release/0.21.xfrom
backport/moduli-suppress/commonly-exact-akita
Closed

Backport of chore: Suppress CVE-2026-41989 into release/0.21.x#6773
hc-github-team-secure-boundary wants to merge 1 commit into
release/0.21.xfrom
backport/moduli-suppress/commonly-exact-akita

Conversation

@hc-github-team-secure-boundary

Copy link
Copy Markdown
Collaborator

Backport

This PR is auto-generated from #6772 to be assessed for backporting due to the inclusion of the label backport/0.21.x.

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@moduli
This person should resolve the merge-conflict(s) by either:

  • Manually completing the cherry picks into this branch
  • Creating a new branch and manually cherry-picking all commits being backported

merge conflict error: POST https://api.github.com/repos/hashicorp/boundary/merges: 409 Merge conflict []

The below text is copied from the body of the original PR.


Description

This PR suppresses a CVE that has no fix available yet. This can be removed once a fix is available.

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.

Overview of commits

@hashicorp-cla-app

Copy link
Copy Markdown

CLA assistant check

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes


temp seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA.
If you have already a GitHub account, please add the email address used for this commit to your account.

Have you signed the CLA already but the status is still pending? Recheck it.

@moduli

moduli commented Jul 31, 2026

Copy link
Copy Markdown
Collaborator

Already in this release branch

@moduli moduli closed this Jul 31, 2026
@moduli
moduli deleted the backport/moduli-suppress/commonly-exact-akita branch July 31, 2026 14:22
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