# CVE-2020-37281: Gravitee API Management through 4.12.22 Default JWT Secret Authentication Bypass

> Attackers can bypass authentication and gain full administrative control by forging JWTs using the default hardcoded secret.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-vh3j-3qjc-g47j

## What is CVE-2020-37281?

CVE-2020-37281 is a critical vulnerability in Gravitee API Management, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Gravitee API Management through 4.12.22 contains an authentication bypass vulnerability that allows unauthenticated remote attackers to impersonate any user by forging JWTs signed with the shipped default jwt.secret. Attackers knowing an existing user ID can sign an HS256 token with that subject and present it as a bearer token to the Management API, impersonating administrators to gain full platform control.

Weakness: CWE-1394 (Use of Default Cryptographic Key)

## Which versions are affected by CVE-2020-37281?


## How do I fix CVE-2020-37281?

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

## Is CVE-2020-37281 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-37281 and fix it if it is affected.

What it is: CVE-2020-37281 is a critical vulnerability in Gravitee API Management, published on 14 Oct 2026. 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-2020-37281 in the wild and no public exploit code.

Affected product: Gravitee API Management. 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-2020-37281/ (Markdown: https://insights.sbomify.com/CVE-2020-37281/index.md)
```

## Sources

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

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