{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-91160 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-91160 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-91160 is a high-severity missing authorization vulnerability in rmyndharis OpenWA, published on 24 Sep 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-91160 and fix it if it is affected.\n\nWhat it is: CVE-2026-91160 is a high-severity missing authorization vulnerability in rmyndharis OpenWA, published on 24 Sep 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-91160 in the wild and no public exploit code.\n\nAffected product: rmyndharis OpenWA. 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-91160/ (Markdown: https://insights.sbomify.com/CVE-2026-91160/index.md)","id":"CVE-2026-91160","markdown":"https://insights.sbomify.com/CVE-2026-91160/index.md","name":"CVE-2026-91160","record":{"aliases":["GHSA-m427-j4h4-9qwj"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WhatsApp API gateway","requires_auth":"low_privilege","summary":"A read-only API key can receive a session pairing QR code, allowing attackers to link external devices and access WhatsApp messages.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"OpenWA is a free, open source, self-hosted WhatsApp API gateway. Prior to 0.23.5, the /events WebSocket gateway delivers the session.qr event to a VIEWER API key that subscribes by event name or through either wildcard subscription form, even though GET /api/sessions/{sessionId}/qr requires the OPERATOR role. When an allowed session is waiting to be paired, the exposed QR lets the key holder link an external device to the WhatsApp account and then read and send messages outside OpenWA and its audit trail. Keys restricted through allowedSessions remain limited to those sessions, and deployments that issue only OPERATOR or ADMIN keys are not affected. This issue is fixed in version 0.23.5.","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":"OpenWA: A read-only API key can receive a session pairing QR over the WebSocket event stream","id":"CVE-2026-91160","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"OpenWA: VIEWER API keys can read WhatsApp group invite codes","id":"CVE-2026-91161"},"packages":[],"prev":{"headline":"Discourse: Stored oEmbed HTML injection via allowed iframe","id":"CVE-2026-91159"},"products":["OpenWA"],"published":"2026-09-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"total"},"state":"PUBLISHED","updated":"2026-10-05","vendors":["rmyndharis"]},"summary":"A read-only API key can receive a session pairing QR code, allowing attackers to link external devices and access WhatsApp messages.","url":"https://insights.sbomify.com/CVE-2026-91160/"}