Homepage

Improper Authorization Affecting zot-fips package, versions <2.1.18-r0

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.43% (37th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-ZOTFIPS-19958004
  • published20 Sept 2026
  • disclosed18 Sept 2026
Report a new vulnerability Found a mistake?

Introduced: 18 Sep 2026

NewCVE-2026-61833  (opens in a new tab)
CWE-285  (opens in a new tab)

How to fix?

Upgrade Minimos:latest zot-fips to version 2.1.18-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream zot-fips package and not the zot-fips package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

zot is a container image and artifact registry based on the Open Container Initiative Distribution Specification. Prior to 2.1.18, the bearer authentication handler in pkg/api/authn.go maps every HTTP method other than GET and HEAD to the push action, so DELETE requests are not checked for the distinct delete permission. Bearer-authenticated requests also bypass the fine-grained DistSpecAuthzHandler path in pkg/api/authz.go, while DeleteManifest and DeleteBlob perform no independent delete-permission check. A remote attacker with a bearer token limited to pull and push actions can therefore delete manifests and blobs within the token's repository scope, making images unavailable and allowing repository history to be altered despite the token lacking delete authorization. This issue is fixed in version 2.1.18.