Loading vulnerability…
CVE-2026-71272 is a server-side request forgery protection bypass in usememos Memos affecting versions up to and including 0.29.1. The flaw is in the webhook dispatch function safeDialContext() in internal/webhook/webhook.go. The function resolves the target hostname with net.DefaultResolver.LookupHost() and validates the returned addresses against reserved or disallowed IP ranges, but it subsequently initiates the connection using the original hostname rather than the already-validated resolved address. Because net.Dialer.DialContext() performs a separate DNS resolution when dialing by hostname, the validation step and the connection step can observe different DNS answers. An attacker who controls DNS responses for the webhook destination can exploit this time-of-check/time-of-use condition by returning an allowed public address during validation and a different internal or otherwise restricted address during the later dial-time lookup, thereby bypassing the intended SSRF protections on webhook delivery.
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.
1 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.