Vulnerability in Zen (CVE-2026-44658)
Summary
Vulnerability in Zen (CVE-2026-44658). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.19.12b or later.
Original description
The description as published by the source.
Zen is a firefox-based browser. Prior to 1.19.12b, RSS feed URLs entered by the user are validated to http: or https: in promptForFeedUrl, but item links inside the feed are not subject to the same restriction. The provider maps each RSS/Atom item link into item.url, filters only for presence and date, and returns the item list. The live-folder manager later creates pinned lazy tabs from these values with gBrowser.addTrustedTab(item.url, ...). This vulnerability is fixed in 1.19.12b.
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-44658 has been found in Zen.
Risk of unauthorized operations or information disclosure. CVSS score: 2.4/10.
What to do: upgrade Zen to 1.19.12b or later.
If unsure, ask your IT team or search "Zen CVE-2026-44658" on the vendor's site.
CVE-2026-44658 (Zen) — CWE-20 / CVSS v3 2.4
Attack vector: remote (network-reachable)
Patched: 1.19.12b — 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-20) exists in Zen.
Check the vendor advisory for the affected versions of Zen.
Severity: Low (CVSS 2.4/10). Risk of unauthorized operations or information disclosure.
Update to 1.19.12b.
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 'Zen' . 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 'Zen' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Zenを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Zen to 1.19.12bステージング環境で 1.19.12b に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov