Authentication bypass via default JWT signing secret
Published May 8, 2026 · Updated May 8, 2026
Authentication bypass in Yeti before 2.1.12 allows remote attackers to forge valid JWTs when the default signing secret remains set. The authentication configuration uses the known value SECRET as the JWT signing key, so token verification accepts attacker-signed claims. Internet or intranet access to the API and an unchanged YETI_AUTH_SECRET_KEY are required; accepted tokens expose data as the forged identity.
Summary
What happened
Authentication bypass in Yeti before 2.1.12 allows remote attackers to forge valid JWTs when the default signing secret remains set. The authentication configuration uses the known value SECRET as the JWT signing key, so token verification accepts attacker-signed claims. Internet or intranet access to the API and an unchanged YETI_AUTH_SECRET_KEY are required; accepted tokens expose data as the forged identity.
The record
- CVE
- CVE-2024-46508
- Published
- May 8, 2026
- Updated
- May 8, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-798, T1550.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 8, 2026CVE publishedPublication date reported by the CVE source.
- May 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo