Loading vulnerability…
Gogs (self-hosted Git service) versions 0.13.4 and below expose attachment upload endpoints without requiring authentication when the global configuration setting RequireSigninView is disabled (the default). In this configuration, remote unauthenticated users can upload arbitrary files to the server via the /releases/attachments and /issues/attachments endpoints (under repositories), effectively bypassing intended access control for attachment uploads. CSRF protections do not prevent the attack in this scenario (per provided content). The issue is fixed in Gogs 0.14.1.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Unknown
Unknown
An unauthenticated access control bypass in GOGS.
A critical missing-authorization issue in Gogs where, when public access is enabled (RequireSigninView disabled), attachment endpoints can be accessed without authentication, enabling arbitrary file upload via /issues/attachments and /releases/attachments.
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.