CVE-2026-52810 is an authorization bypass vulnerability in Gogs affecting Git Smart HTTP handling prior to 0.14.3. The flaw is caused by a logic error in which authorization for POST requests to the Git push endpoint is derived from the client-supplied service query parameter rather than the actual routed operation. As a result, a request targeting git-receive-pack can be evaluated as if it were git-upload-pack when the attacker supplies a read-oriented service value, causing Gogs to apply read-access checks while still dispatching the request to the write handler. This mismatch allows push operations to proceed where only read access should be permitted.
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 valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.