CVE-2024-46508

CVE-2024-46508 is a high-severity vulnerability in Yeti-platform Yeti with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-798.

Key facts

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).

Frequently asked questions

What is 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).
How severe is CVE-2024-46508?
CVE-2024-46508 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2024-46508 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (35th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-46508?
CVE-2024-46508 affects Yeti-platform Yeti. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2024-46508?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2024-46508 have an EU (EUVD) identifier?
Yes. CVE-2024-46508 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-55571.
When was CVE-2024-46508 published?
CVE-2024-46508 was published on 2026-05-08 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Yeti-platform Yeti

All CVEs affecting Yeti-platform Yeti →

Other CWE-798 (Use of Hard-coded Credentials) vulnerabilities

Browse all CWE-798 (Use of Hard-coded Credentials) vulnerabilities →