Open Redirect in Speakr (CVE-2026-45307)
Summary
Vulnerability in Speakr (CVE-2026-45307). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.8.20-alpha or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-45307 has been found in Speakr.
Risk of unauthorized operations or information disclosure. CVSS score: 6.1/10.
What to do: upgrade Speakr to 0.8.20-alpha or later.
If unsure, ask your IT team or search "Speakr CVE-2026-45307" on the vendor's site.
CVE-2026-45307 (Speakr) — CWE-601 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Patched: 0.8.20-alpha — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-601) exists in Speakr.
Check the vendor advisory for the affected versions of Speakr.
Severity: Medium (CVSS 6.1/10). Risk of unauthorized operations or information disclosure.
Update to 0.8.20-alpha.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Speakr' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Speakr' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Speakrを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Speakr to 0.8.20-alphaステージング環境で 0.8.20-alpha に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov