Cross-Site Request Forgery (CSRF) in Warpgate (CVE-2026-44347)
Summary
Vulnerability in Warpgate (CVE-2026-44347). Data can be tampered with by attackers. Mitigation: upgrade to 0.23.3 or later.
Original description
The description as published by the source.
Warpgate is an open source SSH, HTTPS and MySQL bastion host for Linux. Prior to 0.23.3, the SSO flow does not validate the state parameter, which makes it possible for an attacker to trick a user into logging into the attacker's account, possibly convincing them to perform sensitive actions on the attacker's account (such as writing sensitive data to the attacker's SSH target, or logging into an HTTP target that the attacker set up). This vulnerability is fixed in 0.23.3.
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-44347 has been found in Warpgate.
Data can be tampered with by attackers. CVSS score: 5.8/10.
What to do: upgrade Warpgate to 0.23.3 or later.
If unsure, ask your IT team or search "Warpgate CVE-2026-44347" on the vendor's site.
CVE-2026-44347 (Warpgate) — CWE-352 / CVSS v3 5.8
Attack vector: remote (network-reachable)
Patched: 0.23.3 — 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.
CSRF (CWE-352) exists in Warpgate.
Check the vendor advisory for the affected versions of Warpgate.
Severity: Medium (CVSS 5.8/10). Data can be tampered with by attackers.
Update to 0.23.3.
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 'Warpgate' . 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 'Warpgate' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Warpgateを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Warpgate to 0.23.3ステージング環境で 0.23.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov