-
Notifications
You must be signed in to change notification settings - Fork 96
build(deps): bump k8s.io/kubectl from 0.35.3 to 0.36.3 #596
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
dependabot
wants to merge
1
commit into
master
Choose a base branch
from
dependabot/go_modules/k8s.io/kubectl-0.36.3
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔒 Security & Privacy | 🟠 Major | 🏗️ Heavy lift
🧩 Analysis chain
🏁 Script executed:
Repository: meshery/meshsync
Length of output: 7214
🏁 Script executed:
Repository: meshery/meshsync
Length of output: 2441
🌐 Web query:
oras.land/oras-go/v2 v2.6.0 OSV vulnerabilities archive path traversal registry credential token forwarding patched version💡 Result:
The library oras.land/oras-go/v2 version 2.6.0 and earlier are affected by multiple security vulnerabilities [1][2][3]. All these issues are addressed in version 2.6.1, which is the recommended patched version [2][4][5]. Summary of vulnerabilities: Credential and Token Forwarding * Registry Credential Forwarding (CVE-2026-50151): The library failed to validate the Location header during monolithic blob uploads, allowing a malicious registry to redirect the request to a cross-host endpoint while reusing the original Authorization header, leading to credential exfiltration [4][6][7]. A related, residual vulnerability allowed for credential forwarding on manifest redirects [3]. * Bearer Token Realm Validation (GHSA-xf85-363p-868w): The library followed unvalidated Bearer realm URLs, enabling server-side request forgery (SSRF) to internal network endpoints (e.g., IMDS) and permitting TLS downgrade attacks by accepting plaintext http schemes from https-secured registries [1][8]. Path Traversal * Symlink Traversal (CVE-2026-50162): The file store write operation used a lexical check for working directory confinement that did not account for symlink traversal. This allowed an attacker to write files outside the intended working directory [2][9][10]. * Hardlink CWD Resolution (CVE-2026-50163 / GHSA-fxhp-mv3v-67qp): Tar extraction logic incorrectly resolved relative hardlink targets against the process current working directory (CWD) rather than the extraction directory, enabling an attacker to create hardlinks to files outside the intended extract tree [11][12][5]. Version 2.6.1 includes the necessary fixes for these path traversal and credential handling flaws [2][4][5].
Citations:
Upgrade
oras.land/oras-go/v2v2.6.0is reachable throughhelm.sh/helm/v3/pkg/registryand has multiple high-severity vulnerabilities. Upgrade tov2.6.1or later, then rerun the vulnerability scanner.🧰 Tools
🪛 OSV Scanner (2.4.0)
[HIGH] 177-177: oras.land/oras-go/v2 2.6.0: Oras-go: File store write outside workingDir via symlink traversal in oras.land/oras-go
(GO-2026-5879)
[HIGH] 177-177: oras.land/oras-go/v2 2.6.0: Hardlink path traversal during tar extraction in oras.land/oras-go
(GO-2026-5880)
[HIGH] 177-177: oras.land/oras-go/v2 2.6.0: Oras-go: Blob upload vulnerable to credential forwarding via unvalidated Location header in oras.land/oras-go
(GO-2026-5882)
[HIGH] 177-177: oras.land/oras-go/v2 2.6.0: ORAS Go forwards registry credentials across registry redirects in oras.land/oras-go
(GO-2026-5884)
[HIGH] 177-177: oras.land/oras-go/v2 2.6.0: Oras-go: Malicious registry can hijack Bearer token realm to exfiltrate credentials and refresh tokens in oras.land/oras-go
(GO-2026-5885)
[HIGH] 177-177: oras.land/oras-go/v2 2.6.0: oras-go has file store write outside workingDir via symlink traversal
(GHSA-8xwf-rjm4-xvhv)
[HIGH] 177-177: oras.land/oras-go/v2 2.6.0:
oras-gotar extraction: Hardlink entry with relative Linkname escapes extract dir via process CWD resolution(GHSA-fxhp-mv3v-67qp)
[HIGH] 177-177: oras.land/oras-go/v2 2.6.0: oras-go blob upload vulnerable to credential forwarding via unvalidated Location header
(GHSA-jxpm-75mh-9fp7)
[HIGH] 177-177: oras.land/oras-go/v2 2.6.0: ORAS Go forwards registry credentials across registry redirects
(GHSA-vh4v-2xq2-g5cg)
[HIGH] 177-177: oras.land/oras-go/v2 2.6.0: oras-go: Malicious registry can hijack Bearer token realm to exfiltrate credentials and refresh tokens
(GHSA-xf85-363p-868w)
🤖 Prompt for AI Agents
Source: Linters/SAST tools