Is oras.land/oras-go/v2 2.6 vulnerable?
Go · 5 releases from 2.6.0 to 2.6.4 · latest oras.land/oras-go/v2 is 2.7.0 · checked 18 Nov 2026
No known advisories in the last release
oras.land/oras-go/v2 2.6.4, the last 2.6 release, has no known advisories. 14 advisories affect earlier 2.6.x releases, so update to 2.6.4.
go get oras.land/oras-go/v2@v2.6.4Is your project on an affected oras.land/oras-go/v2?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 2.6.x, affecting earlier releases
Arbitrary file write outside file.Store root via symlink-chain bypass in tar extraction (pushDir) in oras.land/oras-go
- Affected
- <2.6.2
- Fixed in
- 2.6.2
Blind SSRF via unvalidated Link header URL in pagination allows internal network probing in oras.land/oras-go
- Affected
- <2.6.2
- Fixed in
- 2.6.2
oras-go: Blind SSRF via unvalidated Link header URL in pagination allows internal network probing
- Affected
- <2.6.2
- Fixed in
- 2.6.2
oras-go: Arbitrary file write outside file.Store root via symlink-chain bypass in tar extraction (pushDir)
- Affected
- <2.6.2
- Fixed in
- 2.6.2
Oras-go: File store write outside workingDir via symlink traversal in oras.land/oras-go
- Affected
- <2.6.1
- Fixed in
- 2.6.1
Hardlink path traversal during tar extraction in oras.land/oras-go
- Affected
- <2.6.2
- Fixed in
- 2.6.2
Oras-go: Blob upload vulnerable to credential forwarding via unvalidated Location header in oras.land/oras-go
- Affected
- <2.6.1
- Fixed in
- 2.6.1
ORAS Go forwards registry credentials across registry redirects in oras.land/oras-go
- Affected
- <2.6.1
- Fixed in
- 2.6.1
Oras-go: Malicious registry can hijack Bearer token realm to exfiltrate credentials and refresh tokens in oras.land/oras-go
- Affected
- <2.6.1
- Fixed in
- 2.6.1
ORAS Go forwards registry credentials across registry redirects
- Affected
- <2.6.1
- Fixed in
- 2.6.1
`oras-go` tar extraction: Hardlink entry with relative Linkname escapes extract dir via process CWD resolution
- Affected
- <2.6.2
- Fixed in
- 2.6.2
oras-go has file store write outside workingDir via symlink traversal
- Affected
- <2.6.1
- Fixed in
- 2.6.1
oras-go blob upload vulnerable to credential forwarding via unvalidated Location header
- Affected
- <2.6.1
- Fixed in
- 2.6.1
oras-go: Malicious registry can hijack Bearer token realm to exfiltrate credentials and refresh tokens
- Affected
- <2.6.1
- Fixed in
- 2.6.1
Every oras.land/oras-go/v2 2.6.x release
Affected: 2.6.0 to 2.6.1. 2.6.2 and later are not affected. Latest oras.land/oras-go/v2: 2.7.0.
| Version | Known advisories |
|---|---|
| oras.land/oras-go/v2 2.6.4 | None |
| oras.land/oras-go/v2 2.6.3 | None |
| oras.land/oras-go/v2 2.6.2 | None |
| oras.land/oras-go/v2 2.6.1 | CVE-2026-85731, CVE-2026-85732, CVE-2026-85732, CVE-2026-85731, CVE-2026-50163, CVE-2026-50163 |
| oras.land/oras-go/v2 2.6.0 | CVE-2026-85731, CVE-2026-85732, CVE-2026-85732, CVE-2026-85731, CVE-2026-50162, CVE-2026-50163, CVE-2026-50151, GO-2026-5884, CVE-2026-48978, GHSA-vh4v-2xq2-g5cg, CVE-2026-50163, CVE-2026-50162, CVE-2026-50151, CVE-2026-48978 |
Which of your client projects are still on oras.land/oras-go/v2 2.6?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact oras.land/oras-go/v2 version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other oras.land/oras-go/v2 versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.