{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-23866 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-23866 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-23866 is a medium-severity server-side request forgery vulnerability in Facebook WhatsApp for Android, published on 1 May 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-23866 and fix it if it is affected.\n\nWhat it is: CVE-2026-23866 is a medium-severity server-side request forgery vulnerability in Facebook WhatsApp for Android, published on 1 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-23866 in the wild and no public exploit code.\n\nAffected product: Facebook WhatsApp for Android. 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-23866/ (Markdown: https://insights.sbomify.com/CVE-2026-23866/index.md)","id":"CVE-2026-23866","markdown":"https://insights.sbomify.com/CVE-2026-23866/index.md","name":"CVE-2026-23866","record":{"aliases":["GHSA-4x7f-p792-g362"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WhatsApp mobile app","requires_auth":"low_privilege","summary":"Incomplete validation in WhatsApp allowed attackers to trigger media processing from arbitrary URLs, potentially invoking OS handlers on victim devices.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Meta","cpe":[{"product":"whatsapp","vendor":"whatsapp"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N/E:F/RL:O/RC:C","version":"3.1"},"cwes":[{"id":"CWE-940","name":"Improper Verification of Source of a Communication Channel"}],"description":"Incomplete validation of AI rich response messages for Instagram Reels in WhatsApp for iOS v2.25.8.0 to v2.26.15.72 and WhatsApp for Android v2.25.8.0 to v2.26.7.10 could have allowed a user to trigger processing of media content from an arbitrary URL on another user’s device, including triggering OS-controlled custom URL scheme handlers. We have not seen evidence of exploitation in the wild.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Server-side request forgery in WhatsApp for Android","id":"CVE-2026-23866","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Use after free in giflib","id":"CVE-2026-23868"},"packages":[],"prev":{"headline":"Integer overflow in FreeType","id":"CVE-2026-23865"},"products":["WhatsApp for Android","WhatsApp for iOS"],"published":"2026-05-01","related":[{"cvss_score":9.8,"headline":"WhatsApp VOIP Stack Buffer Overflow","id":"CVE-2019-3568","kev_date_added":"2022-04-19","published":"2019-05-14"},{"cvss_score":8.2,"headline":"WhatsApp Cross-Site Scripting","id":"CVE-2019-18426","kev_date_added":"2022-05-23","published":"2020-01-21"},{"cvss_score":5.4,"headline":"Meta Platforms WhatsApp Incorrect Authorization","id":"CVE-2025-55177","kev_date_added":"2025-09-02","published":"2025-08-29"},{"cvss_score":9.8,"headline":"Integer overflow in WhatsApp Business for Android","id":"CVE-2022-36934","kev_date_added":null,"published":"2022-09-22"},{"cvss_score":9.8,"headline":"Memory corruption in WhatsApp Business for Android","id":"CVE-2021-24042","kev_date_added":null,"published":"2022-01-04"},{"cvss_score":9.8,"headline":"Memory corruption in WhatsApp Business for Android","id":"CVE-2021-24041","kev_date_added":null,"published":"2021-12-07"},{"cvss_score":9.8,"headline":"Memory corruption in WhatsApp Business for Android","id":"CVE-2021-24026","kev_date_added":null,"published":"2021-04-06"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-01","vendors":["Facebook"]},"summary":"Incomplete validation in WhatsApp allowed attackers to trigger media processing from arbitrary URLs, potentially invoking OS handlers on victim devices.","url":"https://insights.sbomify.com/CVE-2026-23866/"}