CVE-2024-46508 Details
Description
yeti-platform yeti before 2.1.12 allows attackers to generate valid JWT tokens is the secret is not changed (by setting YETI_AUTH_SECRET_KEY to a value other than SECRET).
A vulnerability exists in Yeti Platform versions prior to 2.1.12, where the application uses a static JWT secret 'SECRET' in its Docker deployment. If this secret is not changed, attackers can generate valid JWT tokens, bypassing authentication. The issue arises because the .env file, which contains the secret, is not properly documented or required to be modified during installation, leading to default configurations being used in the wild.
Users are advised to update to Yeti Platform version 2.1.12, where this vulnerability has been patched.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed May 8, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/RhinoSecurityLabs/CVEs/tree/master/CVE-2024-46507 | CISA-ADP | ExploitThird Party Advisory |
| https://rhinosecuritylabs.com/research/cve-2024-46507-yeti-server-side-template-injection-ssti/ | [email protected] | ExploitThird Party Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-798 | Use of Hard-coded Credentials | CISA-ADP |
Affected Products
| Product | Versions |
|---|---|
| yeti-platform yeti | >= 2.0, < 2.1.12 |
CPE
Remediation
| |
Change History
6 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 27, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| May 8, 2026 | Initial Analysis | [email protected] |
| May 8, 2026 | CVE Modified | CISA-ADP |
| May 8, 2026 | New CVE Received | [email protected] |