How to Fix CVE-2026-22662: prompts.chat (Bundle Sibling)

*By Sai Kiran Pandrala*

Last verified: 2026-05-25

CVE-2026-22662 is a sibling vulnerability in the same F prompts.chat advisory bundle as CVE-2026-22661. The same patched build closes every CVE in the bundle, so the remediation procedure for CVE-2026-22662 matches the primary write-up.

What is different about CVE-2026-22662?

prompts.chat prior to commit 1464475 contains a blind server-side request forgery vulnerability in the Wiro media generator that allows authenticated users to perform server-side fetches of user-controlled inputImageUrl parameters. Attackers can exploit this vulnerability by sending POST requests to the /api/media-generate endpoint to probe internal networks, access internal services, and exfiltrate data through the upstream Wiro service without receiving direct response bodies.

Impact is consistent with the bundle: server-side request forgery against internal resources. The patched build closes every code path in the advisory in one update.

How to fix CVE-2026-22662

Apply the patched build per the primary write-up: How to Fix CVE-2026-22661.

For a quick check, confirm the running version of prompts.chat:

# Confirm the installed version via your package manager
dpkg -l | grep -i prompts.chat   # Debian/Ubuntu
rpm -qa | grep -i prompts.chat   # RHEL/CentOS/Rocky

Frequently asked questions

Is CVE-2026-22662 being actively exploited?

Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That status can change, so monitor the vendor advisory and the KEV catalog if the system is exposed.

How severe is CVE-2026-22662?

CVSS rates it 5.3 (Medium). Use that score to set your patch priority alongside the other items in your queue.

Do I have to take prompts.chat offline to apply the patch?

It depends on the deployment. High-availability or clustered installs can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.

What if my vulnerability scanner still flags CVE-2026-22662 after I patch?

Re-run the scan after a service restart, then confirm the scanner's plugin set is up to date. Some scanners detect by banner version only and lag the official fix metadata by a release.

References

• Official vendor advisory: https://github.com/f/prompts.chat/pull/1102
• NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-22662
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
• Primary write-up: How to Fix CVE-2026-22661

*Written by Sai Kiran Pandrala. Last verified 2026-05-25. Part of the F prompts.chat advisory bundle. Full procedure at how-to-fix-cve-2026-22661.*