CVE-2026-44347: warp-tech warpgate · Cross-Site Request Forgery (CSRF)
Affects warp-tech warpgateSource CVE Database V5
Not known to be exploited · CVSS 5.8 Medium : upgrade to 0.23.3 when convenient.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.23.3
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 12 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 17 Nov 2026.
What to do
Upgrade warpgate and warp-tech/warpgate to 0.23.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| warp-techwarpgate | Affected
| Fixed in
|
GitHubwarp-tech/warpgatepkg:github/warp-tech/warpgateOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Warpgate to version 0.23.3 or later, where the vulnerability is fixed by proper validation of the state parameter in the SSO flow. Patch status is not explicitly confirmed beyond the version fix note, so check vendor advisories for the latest remediation guidance.
Description
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.