Secuno
ENNL
Book demo

CVE-2024-46508

Yeti-platform Yeti hard-coded credentials

7.5 HIGHPublic exploitEPSS 0.43%
  1. Published8 May 2026

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

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityNone
AvailabilityNone
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected products

Yeti-platform Yeti≥ 2.0 < 2.1.12

Remediation

Fixed in
Yeti-platform Yeti≥ 2.1.12

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-1095669.8
Rapyd Admin from 9.0.0 before 9.20.0 contains a hard-coded credentials vulnerability…
CVE-2026-1087539.4
Agnaistic agnai through 1.0.555 contains a hard-coded credentials vulnerability in…
CVE-2026-1052789.8
The published Docker image for openPDC includes a fixed administrative credential with…
CVE-2026-842508.4
IBM Guardium Data Protection 12.2 is vulnerable due to weak cryptographic protection…
CVE-2026-622529.8
Homer is open source telecom observability software. Prior to version 11.0.283, on…
CVE-2026-1021618.8
An unauthenticated attacker located on an adjacent private network (or any attacker…

Frequently asked

Is CVE-2024-46508 being actively exploited?

CVE-2024-46508 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.43%.

How severe is CVE-2024-46508?

CVE-2024-46508 has a CVSS 3.1 base score of 7.5, rated high. EPSS estimates a 0.43% probability of exploitation.

Which products are affected by CVE-2024-46508?

Affected products include Yeti-platform Yeti.

How do I fix CVE-2024-46508?

Upgrade affected software to a fixed version, for example Yeti-platform Yeti 2.1.12 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-46508 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.