Skip to main content
VulnerabilityPublished

CVE-2026-45307: murtaza-nasir speakr · Open Redirect

Affects murtaza-nasir speakrSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.1 Medium : upgrade to 0.8.20-alpha when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.8.20-alpha
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 May 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 30 Oct 2026.

What to do

Upgrade murtaza-nasir speakr to 0.8.20-alpha.

Affected software

ProductAffectedFixed in
murtaza-nasirspeakrAffected
  • <0.8.20-alpha
Fixed in
  • 0.8.20-alpha
GitHubmurtaza-nasir/speakrpkg:github/murtaza-nasir/speakrOther threatsAffected
  • =0.8.20-alpha
Fixed in–

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

AI-suggested

This vulnerability is fixed in speakr version 0.8.20-alpha. Users should upgrade to this version or later to remediate the issue. Patch status is not explicitly confirmed beyond the fix in 0.8.20-alpha; users should verify with the vendor for the latest remediation guidance.

Description

Speakr is a personal, self-hosted web application designed for transcribing audio recordings. Prior to 0.8.20-alpha, the is_safe_url() helper used to validate post-login redirect targets applied urljoin(request.host_url, target) before parsing, while the controller passed the raw target to redirect(). A scheme-relative input such as ////evil.com resolved to a same-host URL during validation but was emitted verbatim in the Location header, where the browser interpreted it as a network-path-relative redirect to an attacker-controlled host. This vulnerability is fixed in 0.8.20-alpha.

References

Community reviews

Loading reviews…