# CVE-2021-36209: Auth bypass in n/a

> Attackers can take over user accounts during the password reset process in JetBrains Hub.

- **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:** 6 Aug 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-rh6h-f4gj-hpgv

## What is CVE-2021-36209?

CVE-2021-36209 is a critical authentication bypass vulnerability in n/a, published on 6 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In JetBrains Hub before 2021.1.13389, account takeover was possible during password reset.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password)

## Which versions are affected by CVE-2021-36209?

It affects 1 product.


Products: Jetbrains Hub.

## How do I fix CVE-2021-36209?

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

## Is CVE-2021-36209 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-50242](https://insights.sbomify.com/CVE-2026-50242/): Auth bypass in Hub (critical 10.0)
- [CVE-2026-56141](https://insights.sbomify.com/CVE-2026-56141/): Weak cryptography in Hub (critical 9.8)
- [CVE-2022-25262](https://insights.sbomify.com/CVE-2022-25262/): Auth bypass in n/a (critical 9.8)
- [CVE-2021-43183](https://insights.sbomify.com/CVE-2021-43183/): Security feature bypass in n/a (critical 9.8)
- [CVE-2026-56142](https://insights.sbomify.com/CVE-2026-56142/): Privilege escalation in Hub (critical 9.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-36209 and fix it if it is affected.

What it is: CVE-2021-36209 is a critical authentication bypass vulnerability in n/a, published on 6 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-36209 in the wild and no public exploit code.

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-2021-36209/ (Markdown: https://insights.sbomify.com/CVE-2021-36209/index.md)
```

## Sources

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

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