CVE-2026-126807 json
WuzAPI through 1.1.0 Cross-Tenant Information Disclosure via /chat/history
published 13h ago modified 13h ago also EUVD-2026-124022
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
WuzAPI through 1.1.0 contains a cross-tenant information disclosure vulnerability in the GetHistory handler that allows authenticated users to view other tenants' chat metadata. Attackers with message history enabled can request GET /chat/history with chat_jid=index to list every user's internal ID, stored chat JIDs, and last-message times.
Patch / fix
Is CVE-2026-126807 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 5.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N |
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| CNA | 4.0 | 5.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected products
- asternic wuzapi
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
References
-
github.com
/asternic/wuzapi/commit/f5332fa21b7c8a742f9ee565328ea776ad0c8040
patch
-
github.com
/asternic/wuzapi/issues/407
issue-tracking
-
github.com
/asternic/wuzapi/blob/v1.1.0/handlers.go#L7269-L7296
technical-description
-
github.com
/asternic/wuzapi/blob/v1.1.0/routes.go#L139
technical-description
-
hackmd.io
/@hieund/wuzapi-chat-history-index-cross-tenant-idor
third-party-advisory
-
vulncheck.com
/advisories/wuzapi-through-1.1.0-cross-tenant-information-disclosure-via-chat-history
third-party-advisory
Sources
- CVE List CVE-2026-126807
- NVD CVE-2026-126807
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.