Notation vulnerable to denial of service from high number of artifact signatures

Exploitation

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

CVSS

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

EPSS

• CVE-2023-33957: 0.51% estimated exploitation activity in the next 30 days; percentile 43.24 (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 An attacker who controls or compromises a registry can make the registry serve an infinite number of signatures for the artifact, causing a denial of service to the host machine running notation verify. Patches The problem has been fixed in the release v1.0.0-rc.6. Users should upgrade their notation packages to v1.0.0-rc.6 or above. Workarounds User should use secure and trusted container registries. Credits The notation project would like to thank Adam Korczynski (@AdamKorcz) for responsibly disclosing the issue found during an security audit (facilitated by OSTIF and sponsored by CNCF) and Shiwei Zhang (@shizhMSFT) for root cause analysis.

Published by the source

6 Jun 2023, 16:43 UTC

Last modified by the source

1 Mar 2024, 15:18 UTC

Source last checked

26 Oct 2026, 15:03 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-9m3v-v4r5-ppx7

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

# Patch Next advisory brief: CVE-2023-33957

Advisory: Notation vulnerable to denial of service from high number of artifact signatures
IDs: CVE-2023-33957, GHSA-9m3v-v4r5-ppx7
Record: https://patchnext.com/advisories/cve-2023-33957 (revision 1, source checked 26 Oct 2026, 15:03 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.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/notaryproject/notation 1.0.0-rc.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/notaryproject/notation: affected < 1.0.0-rc.6; fixed in 1.0.0-rc.6

## Suggested inspection (read-only)
- Go github.com/notaryproject/notation: 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/notaryproject/notation.
- 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-9m3v-v4r5-ppx7 (GitHub-reviewed advisory GHSA-9m3v-v4r5-ppx7 lists affected ranges: Go github.com/notaryproject/notation >=0 <1.0.0-rc.6)

Commands are suggestions: review each one before running it.