# CVE-2026-126807: WuzAPI through 1.1.0 Cross-Tenant Information Disclosure via /chat/history

> Authenticated WuzAPI users can list other tenants' chat metadata, including user IDs and last-message times, when message history is enabled.

- **Severity:** Medium 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 11 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-744h-gprq-h6r9

## What is CVE-2026-126807?

CVE-2026-126807 is a medium-severity missing authorization vulnerability in asternic wuzapi, published on 11 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-126807?

Only installations with a non-default setting turned on are exposed.


## How do I fix CVE-2026-126807?

No fix has been published for CVE-2026-126807 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-126807 being exploited?

There is no known exploitation of CVE-2026-126807 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-126807 and fix it if it is affected.

What it is: CVE-2026-126807 is a medium-severity missing authorization vulnerability in asternic wuzapi, published on 11 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-126807 in the wild and no public exploit code.
Exposure: Only installations with a non-default setting turned on are exposed.

Affected product: asternic wuzapi. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-126807/ (Markdown: https://insights.sbomify.com/CVE-2026-126807/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-126807
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-126807
- OSV: https://osv.dev/vulnerability/CVE-2026-126807

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-126807/
Summaries are generated and may contain mistakes; the official description above is the record.
