CVE-2026-91160

HIGHPre-NVD 8.28.2
EchelonGraph scoreLOW confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: secondary
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 8.2Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.2
EG Score
8.2(low)
EG Risk
41(Track)
EG Risk 41/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity82% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
—
EPSS %ILE
—
KEV
Not listed

Published

September 24, 2026

Last Modified

September 24, 2026

Advisory Details (5)

Auto-updated Sep 24, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

v0.23.5

Patch available: rmyndharis/OpenWA v0.23.5

https://github.com/rmyndharis/OpenWA/releases/tag/v0.23.5
github_commit

commit b9d9ea1c57bd (rmyndharis/OpenWA)

Fix landed in rmyndharis/OpenWA commit b9d9ea1c57bd — awaiting tagged release

https://github.com/rmyndharis/OpenWA/commit/b9d9ea1c57bde98b7833a5d6e482998703667ef0
github_commit

commit acc23c3803c0 (rmyndharis/OpenWA)

Fix landed in rmyndharis/OpenWA commit acc23c3803c0 — awaiting tagged release

https://github.com/rmyndharis/OpenWA/commit/acc23c3803c07f43791a92e8e48456572fd69bdc
github_pr

fix(events): withhold session.qr from keys below OPERATOR

Fix merged in rmyndharis/OpenWA PR #1602 on 2026-09-14 — awaiting tagged release

https://github.com/rmyndharis/OpenWA/pull/1602
github Patch Available

A read-only API key can receive a session pairing QR over the WebSocket event stream · Advisory · rmyndharis/OpenWA · GitHub

Affected: 0.23.5. The gateway now filters

https://github.com/rmyndharis/OpenWA/security/advisories/GHSA-m427-j4h4-9qwj

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 3× in last 7d / 3× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-24 17:33 UTCEG score recompute
  2. 2026-09-24 16:47 UTCEG score recompute
  3. 2026-09-24 16:46 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-91160?
CVE-2026-91160 is a high vulnerability published on September 24, 2026. 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…
When was CVE-2026-91160 disclosed?
CVE-2026-91160 was first published in the National Vulnerability Database on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-91160?
CVE-2026-91160 has a CVSS v3 base score of 8.2 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-91160?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-91160, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-91160

Explore →

Is Your Infrastructure Affected by CVE-2026-91160?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.