Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

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

61
This week
HIGH 7.3REMOTEUPGRADE

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

A SSTI (server side template injection) vulnerability in the custom template export function in yeti-platform yeti before 2.1.12 allows attackers to execute code on the application server.

Why this priority

  • High severity
  • EPSS top 10%: very likely to be exploited
  • Public exploit reference
  • CISA SSVC: automatable with total technical impact
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score7.3 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance3.9% (top 10%)
CISA exploited listNo
WeaknessCWE-94
Published2026-05-08
Last modified2026-06-17
Publisher (CNA): MITRE · Vendor: yeti-platform

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

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.

Exact fixes by distribution

Fedora 46 · fzssh · FIXED · 1.4.0-2.fc46 · FEDORA-2026-8004fcd067 · source
sudo dnf upgrade --advisory=FEDORA-2026-8004fcd067

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

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-46507?

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

Is CVE-2024-46507 being exploited?

CVE-2024-46507 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-46507 affect?

CVE-2024-46507 affects yeti. Severity is high (CVSS 7.3). A SSTI (server side template injection) vulnerability in the custom template export function in yeti-platform yeti before 2.1.12 allows attackers to execute code on the application server.

How urgent is CVE-2024-46507?

Priority 61/100. High severity; EPSS top 10%: very likely to be exploited; Public exploit reference; CISA SSVC: automatable with total technical impact; Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.