Vulnerability · CVE-2024-46508
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).
Published May 8, 2026 · catalog updated Jun 17, 2026 · yeti-platform yeti before 2.1.12
Check if you run it
No confirmed exploitation is on record for CVE-2024-46508. EPSS is 0.43%. Act only if a listed version of yeti-platform yeti before 2.1.12 is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (yeti-platform yeti before 2.1.12).
- No version range is stored. A customer cannot check an installed version against this record.
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- High7.5
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.43%
- Remediation
- Advisory link
- Affected products
- cpe yeti-platform/yeti
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).
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- cpe yeti-platform/yetiversion unspecified
How to fix CVE-2024-46508
Recommended remediation
A patch or advisory reference is linked. Open the original publisher for availability by product version.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2024-46508. EPSS is 0.43%. Act only if a listed version of yeti-platform yeti before 2.1.12 is installed.
Which versions are affected?
Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-798: Use of Hard-coded Credentials. EPSS 0.43%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
May 8, 2026 · NIST NVD
Detected
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).
Jun 17, 2026 · NIST NVD
Updated
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).
Sources
- CVE.orgVulnerability recordCVE-2024-46508
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2024-46508
30-day exploitation probability 0.4%
first.org - NIST NVDVulnerability recordCVE-2024-46508
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).
nvd.nist.gov
References
Freshness
Last verified in this catalog Oct 16, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.