CVE-2026-22664: prompts.chat · Server-Side Request Forgery (SSRF)
Affects prompts.chatSource CVE Database V5
Not known to be exploited · CVSS 7.1 High : upgrade to 30a8f0470e0ba45e6be9c9f55220f4a9a6b91c99 soon.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 30a8f0470e0ba45e6be9c9f55220f4a9a6b91c99
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 Oct 2026.
What to do
Upgrade prompts.chat to 30a8f0470e0ba45e6be9c9f55220f4a9a6b91c99.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| prompts.chat | Affected
| Fixed in
|
GitHubf/prompts.chatpkg:github/f/prompts.chatOther threats | Affected
| Fixed in– |
GitHubprompts.chatpkg:github/prompts.chatOther 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
If you cannot patch yet, restrict authenticated user access to trusted parties and monitor for suspicious activity related to the Fal.ai media status polling feature.
Description
prompts.chat prior to commit 30a8f04 contains a server-side request forgery vulnerability in the Fal.ai media status polling feature that allows authenticated users to perform arbitrary outbound requests by supplying attacker-controlled URLs in the token parameter. Attackers can exploit the lack of URL validation to disclose the FAL_API_KEY in the Authorization header, enabling credential theft, internal network probing, and abuse of the victim's Fal.ai account.