Skip to main content
← Vulnerabilities

Dreeve before 5.8.0 Missing Authentication in Strava Webhook POST Handler

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

6.9MediumCNA
Exploited
No known exploitation
Fix
Fixed in 5.8.0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 5.8.0.

24Pcve.now Index 24 of 100 · methodology v3 · provisional
  • Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Data gap: No advisory context yet
  • Reach?/20Reach: unknown (data gap). No tracked technology or package matched
  • Severity6.9/10CVSS 6.9
  • No patch0/5No signal

What would change the score

  • Would score about 69 if added to CISA KEV
  • Would score about 64 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

CVE-2026-121545 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.9 (medium) and affects dreeve; fixed in 5.8.0.

Published
Last modified
Published
Not listed in CISA KEV
24/100 · provisional
Fix
Fixed in 5.8.0
None on Exploit-DB, Metasploit or GitHub

Summary

Dreeve, a fitness data application, is affected by a flaw in its Strava webhook handler that lacks authentication checks. An unauthenticated attacker could send forged webhook events that cause imported activities and their data to be permanently deleted.

Read the original description

Dreeve before 5.8.0 contains a missing authentication vulnerability in StravaWebhookRequestHandler::handleEvent that allows unauthenticated attackers to forge Strava webhook events without signature, verify-token or owner_id checks. Attackers can send forged delete events with a known public Strava activity id to the webhook URL, causing permanent deletion of imported activities and their streams.

What to do

  • Upgrade to a fixed version: 5.8.0.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • robiningelbrecht dreeve

    fixed in 5.8.0

Evidence 7

  1. Patch
  2. Patch
  3. Report
  4. Repository
  5. Repository
Show all 7 sourcesShow fewer sources
  1. Repository
  2. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-121545

Is CVE-2026-121545 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-121545?

dreeve: before 5.8.0.Source: cve.now feed data

How do I fix CVE-2026-121545?

Upgrade to a fixed version: 5.8.0.Source: cve.now feed data