Zip slip directory exploit in github.com/deislabs/oras

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.7 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N

EPSS

• CVE-2021-21272: 1.47% estimated exploitation activity in the next 30 days; percentile 73.71 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact The directory support (#55) allows the downloaded gzipped tarballs to be automatically extracted to the user-specified directory where the tarball can have symbolic links and hard links. A well-crafted tarball or tarballs allow malicious artifact providers linking, writing, or overwriting specific files on the host filesystem outside of the user-specified directory unexpectedly with the same permissions as the user who runs oras pull. Precisely, the following users of the affected versions are impacted - oras CLI users who runs oras pull. - Go programs, which invokes github.com/deislabs/oras/pkg/content.FileStore. Patches The problem has been patched by the PR linked with this advisory. Users should upgrade their oras CLI and packages to 0.9.0. Workarounds For oras CLI users, there is no workarounds other than pulling from a trusted artifact provider. For oras package users, the workaround is to not use github.com/deislabs/oras/pkg/content.FileStore, and use other content…

Published by the source

15 Feb 2022, 00:32 UTC

Last modified by the source

14 Feb 2023, 14:55 UTC

Source last checked

26 Oct 2026, 14:55 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-g5v4-5x39-vwhx

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2021-21272

Advisory: Zip slip directory exploit in github.com/deislabs/oras
IDs: CVE-2021-21272, GHSA-g5v4-5x39-vwhx
Record: https://patchnext.com/advisories/cve-2021-21272 (revision 1, source checked 26 Oct 2026, 14:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/deislabs/oras 0.9.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/deislabs/oras: affected < 0.9.0; fixed in 0.9.0

## Suggested inspection (read-only)
- Go github.com/deislabs/oras: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/deislabs/oras.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-g5v4-5x39-vwhx (GitHub-reviewed advisory GHSA-g5v4-5x39-vwhx lists affected ranges: Go github.com/deislabs/oras >=0 <0.9.0)

Commands are suggestions: review each one before running it.