CVE-2024-46508: yeti-platform yeti before 2.1.12 allows attackers to generate valid JWT tokens is the secret is not changed (b

This week

HIGH 7.5REMOTEUPGRADE

CVE-2024-46508 is a high-severity flaw (CVSS 7.5) affecting yeti. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 63%)
CISA exploited list	No
Weakness	CWE-798
Published	2026-05-08
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: yeti-platform

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-05-08 06:16 UTCPublished CVE record published
2026-06-17 07:55 UTCUpdated Record last modified

yeti-platform yeti UPGRADE

Affected: >= 2.0 and < 2.1.12

Fixed in: 2.1.12

Safe to downgrade to: a release before 2.0

1. Check installed version

apt-cache policy yeti || rpm -q yeti || yeti --version

2. UPGRADE to 2.1.12 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade yeti

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade yeti

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 2.0 (Debian / Ubuntu)

apt-cache madison yeti sudo apt install yeti=<VERSION_BEFORE_2.0> sudo apt-mark hold yeti

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list yeti sudo dnf downgrade yeti-<VERSION_BEFORE_2.0> sudo dnf versionlock add yeti

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-46508?

yeti: upgrade to 2.1.12. Exact commands for each OS are on this page.

Is CVE-2024-46508 being exploited?

CVE-2024-46508 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-46508 affect?

CVE-2024-46508 affects yeti. Severity is high (CVSS 7.5). 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 urgent is CVE-2024-46508?

Priority 45/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2024-46507 HIGH 7.3 UPGRADE A SSTI (server side template injection) vulnerability in the custom template export function in yeti-platform

References

← Back to latest CVEs