Loading vulnerability…
In Gogs (self-hosted Git service) versions 0.13.3 and earlier, the wiki update/rename flow contains a path traversal flaw in the updateWikiPage function. An authenticated user with write access to a repository’s wiki can manipulate the old_title parameter in the wiki editing/rename form to traverse outside the intended wiki directory. The server then resolves the attacker-influenced path (with a .md suffix appended) and deletes it via os.Remove, enabling deletion of arbitrary server-side files reachable by traversal that match the effective target naming (i.e., with .md appended). The issue is fixed in 0.13.4 and 0.14.0+dev.
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.