# CVE-2026-36537: Auth bypass in n/a

> Remote attackers can bypass OAuth authentication by manipulating user identity data to take over any existing account on the ThingsBoard platform.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jun 2026
- **Updated:** 16 Jun 2026
- **Also known as:** GHSA-cjqr-jj24-mfr6

## What is CVE-2026-36537?

CVE-2026-36537 is a critical authentication bypass vulnerability in n/a, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ThingsBoard v4.3.0.1 is vulnerable to an authentication bypass during the OAuth authorization code exchange. The application improperly trusts user-supplied identity data within the user parameter of the /login/oauth2/code/ endpoint. By manipulating the email address in this JSON object, a remote attacker can bypass authentication and gain full access to any existing user account on the platform without possessing the target user's credentials. This results in a complete account takeover.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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


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

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

## Is CVE-2026-36537 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-36537 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-36537 is a critical authentication bypass vulnerability in n/a, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-36537 exists.

Affected product: n/a. 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-36537/ (Markdown: https://insights.sbomify.com/CVE-2026-36537/index.md)
```

## Sources

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

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