Gravitee API Management: Authentication bypass via forged JWTs with default secret
Summary
Gravitee API Management through 4.12.22 ships with a default jwt.secret. An unauthenticated remote attacker who knows an existing user ID can sign a JWT with this secret and use it as a bearer token against the Management API. This allows impersonation of administrators and full control of the platform.
Affected
- Gravitee API Management 0 through 4.12.22 (default configuration with the shipped jwt.secret)
Fixed in
- Unknown. No fixed version was confirmed in the sources reviewed.
Workaround
- Replace the default jwt.secret with a unique, long random value and restart the service.
- Restrict access to the Management API to administrative networks or a VPN.
Exploitation
- Attack requires only network access to the Management API and knowledge of an existing user ID; no prior authentication is needed.
- Known exploitation in the wild: Unknown. No public proof of concept was found.
- CISA SSVC: Exploitation none, Automatable no, Technical Impact total.
Our recommendation
- Identify all Gravitee API Management instances and their versions.
- Check whether jwt.secret is still the shipped default; if so, replace it immediately and restart.
- Restrict Management API access to admin networks.
- Check the Gravitee advisories and release notes for a fixed version and upgrade once available.
- Monitor for unexpected administrator activity and re-check exploitation status before closing this item.
Public exploits
PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.
Research sources
- VulnCheck advisory www.vulncheck.com
- Gravitee gravitee.yml at 4.12.22 github.com
- Gravitee BasicSecurityConfigurerAdapter.java at 4.12.22 github.com
- Gravitee issue #4204 github.com
- Gravitee production best practices: authentication documentation.gravitee.io
- VulDB entry 419898 vuldb.com
Researched and written up in English and German by an AI (Claude by Anthropic) based on NVD, CISA, EPSS and the sources listed. The vendor information is authoritative. Researched on 31 Oct 2026, 04:37.
Original description (NVD)
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.
NVD references (6)
- https://github.com/gravitee-io/gravitee-api-management/blob/4.12.22/gravitee-apim-rest-api/gravitee-apim-rest…
- https://github.com/gravitee-io/gravitee-api-management/blob/4.12.22/gravitee-apim-rest-api/gravitee-apim-rest…
- https://github.com/gravitee-io/gravitee-api-management/blob/4.12.22/helm/values.yaml#L103
- https://github.com/gravitee-io/gravitee-docs/blob/master/pages/apim/3.x/how-tos/how-to-general-configuration.…
- https://github.com/gravitee-io/issues/issues/4204
- https://www.vulncheck.com/advisories/gravitee-api-management-through-4.12.22-default-jwt-secret-authenticatio…
Sources
The tracker combines official, freely usable data sources – updated continuously:
- NVD (NIST) – CVEs, rating (CVSS), affected products
- CISA KEV – vulnerabilities confirmed by CISA as actively exploited
- CISA Vulnrichment – CISA assessment (SSVC) in the official CVE record
- FIRST EPSS – probability of exploitation
- Microsoft MSRC – Patch Tuesday: vulnerabilities, severity, updates
- PoC-in-GitHub – public proof-of-concept repositories
- Metasploit (Rapid7) – modules of the Metasploit Framework
- Exploit-DB (OffSec) – archive of public exploits (links only)
- Patch days: official vendor pages (linked per vendor) (Vendor patch days)
This product uses data from the NVD API but is not endorsed or certified by the NVD. EPSS data © FIRST.org.
Affected? We can help.
We check whether your systems are affected, install updates and close the gap – continuously with the System Health Checker if you wish.
