CVE-2026-71271
Webhook validation allows SSRF to localhost via 0.0.0.0 bypass.
Is CVE-2026-71271 being exploited?
Not confirmed. CVE-2026-71271 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.24% probability of exploitation in the next 30 days.
How severe is CVE-2026-71271?
CVE-2026-71271 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-71271?
Not known from our data. No patch reference has been recorded for CVE-2026-71271, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-71271 affect?
CVE-2026-71271 affects Memos (server webhook URL validation). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-71271?
Block 0.0.0.0, validate IsUnspecified(), restrict outbound localhost access and update Memos when patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Server-side request forgery: attacker can make the server call localhost/internal services (127.0.0.1) via http://0.0.0.0:PORT, exposing internal APIs and admin endpoints.
Patch when possible
- affected<= 0.29.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.