{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-22663 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-22663 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-22663 is a high-severity missing authorization vulnerability in f prompts.chat, published on 3 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-22663 and fix it if it is affected.\n\nWhat it is: CVE-2026-22663 is a high-severity missing authorization vulnerability in f prompts.chat, published on 3 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-22663 in the wild and no public exploit code.\n\nAffected product: f prompts.chat. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-22663/ (Markdown: https://insights.sbomify.com/CVE-2026-22663/index.md)","id":"CVE-2026-22663","markdown":"https://insights.sbomify.com/CVE-2026-22663/index.md","name":"CVE-2026-22663","record":{"aliases":["GHSA-hphm-9vp4-h223"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"prompts.chat web app","requires_auth":"none","summary":"Attackers can access private prompt data and metadata due to missing authorization checks in prompts.chat API endpoints.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"prompts.chat","vendor":"fka"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"prompts.chat prior to commit 7b81836 contains multiple authorization bypass vulnerabilities due to missing isPrivate checks across API endpoints and page metadata generation that allow unauthorized users to access sensitive data associated with private prompts. Attackers can exploit these missing authorization checks to retrieve private prompt version history, change requests, examples, current content, and metadata including titles and descriptions exposed via HTML meta tags.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"prompts.chat Authorization Bypass Information Disclosure","id":"CVE-2026-22663","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"prompts.chat SSRF via Fal.ai Media Status Polling","id":"CVE-2026-22664"},"packages":[],"prev":{"headline":"prompts.chat Blind SSRF via media-generate","id":"CVE-2026-22662"},"products":["prompts.chat"],"published":"2026-04-03","related":[{"cvss_score":8.6,"headline":"prompts.chat Path Traversal via Skill File Handling","id":"CVE-2026-22661","kev_date_added":null,"published":"2026-04-03"},{"cvss_score":8.6,"headline":"prompts.chat Identity Confusion via Case-Sensitive Username Handling","id":"CVE-2026-22665","kev_date_added":null,"published":"2026-04-03"},{"cvss_score":7.1,"headline":"prompts.chat SSRF via Fal.ai Media Status Polling","id":"CVE-2026-22664","kev_date_added":null,"published":"2026-04-03"},{"cvss_score":5.3,"headline":"prompts.chat Blind SSRF via media-generate","id":"CVE-2026-22662","kev_date_added":null,"published":"2026-04-03"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-14","vendors":["f"]},"summary":"Attackers can access private prompt data and metadata due to missing authorization checks in prompts.chat API endpoints.","url":"https://insights.sbomify.com/CVE-2026-22663/"}