Loading vulnerability…
CVE-2026-69865 is a CWE-639 authorization-bypass vulnerability in the exclusively hosted Microsoft Container Registry service. The flaw arises from authorization decisions that use a user-controlled key, enabling an unauthenticated attacker to bypass intended repository access controls over the network and elevate privileges. The CVSS v3.1 vector is AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A user-controlled-key authorization bypass in Microsoft Container Registry that enables privilege escalation and could facilitate malicious container-image pushes.
An authorization-bypass vulnerability in Microsoft Container Registry caused by a user-controlled key, enabling an unauthenticated attacker to elevate privileges over the network.
An authorization-bypass vulnerability (CWE-639) in Microsoft Container Registry caused by a user-controlled key. It may allow an unauthenticated network attacker to elevate privileges. The listed CVSS v3.1 vector is AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.