cve.bz

CVE-2026-61833 project-zot zot: Improper Authorization

8.1 highEPSS 0.8%Fix available

High (8.1) in project-zot zot. EPSS 0.8% estimated probability of exploitation activity in the next 30 days. Fixed in zotregistry.dev/zot/v2 2.1.18.

On this page
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.

Severity

CVSS 3.1

8.1 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
EPSS
0.8% (unchanged from 0.8% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 58th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-09-23. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-285 Improper Authorization
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • zotregistry.dev/zot/v2 (Go): fixed in 2.1.18

Ask an AI about this CVE

Show the promptExplain CVE-2026-61833 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-61833?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-61833?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-61833 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
project-zot zot< 2.1.18

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-qg67-7m6v-qg25Gozotregistry.dev/zot/v2<2.1.182.1.18
GO-2026-6527Gozotregistry.dev/zotall versionsno fix published
GO-2026-6527Gozotregistry.dev/zot/v2<2.1.182.1.18

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-285 (16).

References

Check your stackJSON