Skip to main content
VulnerabilityPublished

CVE-2026-121545: robiningelbrecht dreeve · Insufficient Verification of Data Authenticity

Affects robiningelbrecht dreeveSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.9 Medium : upgrade to 5.8.0 when convenient.

Data as of 3 Nov 2026, 15:43 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.06.9
CNA (VulnCheck)CVSS 3.16.5
Patch
Available – fixed in 5.8.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.

What to do

Upgrade robiningelbrecht dreeve to 5.8.0.

Affected software

ProductAffectedFixed in
robiningelbrechtdreeveAffected
  • <5.8.0
Fixed in
  • 5.8.0
Packagistdreevepkg:composer/dreeveOther threatsAffected
  • <5.8.0
Fixed in
  • 5.8.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade dreeve to version 5.8.0 or later, where this authentication vulnerability has been fixed. No other mitigation or workaround is indicated by the vendor advisory.

Description

Dreeve versions before 5.8.0 have a vulnerability in the StravaWebhookRequestHandler::handleEvent function that lacks proper authentication checks. This allows unauthenticated attackers to forge Strava webhook events without verifying signatures, tokens, or owner IDs. Exploitation can lead to attackers sending forged delete events with known public Strava activity IDs to the webhook URL, resulting in permanent deletion of imported activities and their associated data streams.

References

Community reviews

Loading reviews…