CVE-2026-39087: ntfy · Code Injection
Affects ntfySource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 2.22.0 as a priority.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.22.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 23 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade ntfy and binwiederhier/ntfy to 2.22.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ntfyntfy | Affected
| Fixed in
|
GitHubbinwiederhier/ntfypkg:github/binwiederhier/ntfyOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
No specific temporary mitigations are documented in the available data.
Description
ntfy before 2.22.0 allows SSRF because of an unanchored regular expression.