SFTPGo vulnerable to recovery codes abuse

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

EPSS

• CVE-2022-36071: 0.55% estimated exploitation activity in the next 30 days; percentile 45.90 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact SFTPGo WebAdmin and WebClient support login using TOTP (Time-based One Time Passwords) as a seconday authentication factor. Because TOTPs are often configured on mobile devices that can be lost, stolen or damaged, SFTPGo also supports recovery codes. These are a set of one time use codes that can be used instead of the TOTP. In SFTPGo versions from v2.2.0 to v2.3.3 recovery codes can be generated before enabling two-factor authentication. An attacker who knows the user's password could potentially generate some recovery codes and then bypass two-factor authentication after it is enabled on the account at a later time. Patches Fixed in v2.3.4. Recovery codes can now only be generated after enabling two-factor authentication and are deleted after disabling it. Workarounds Regenerate recovery codes after enabling two-factor authentication. References https://github.com/drakkan/sftpgo/issues/965

Published by the source

16 Sep 2022, 21:05 UTC

Last modified by the source

27 Jan 2023, 05:03 UTC

Source last checked

26 Oct 2026, 14:54 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-54qx-8p8w-xhg8

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-36071

Advisory: SFTPGo vulnerable to recovery codes abuse
IDs: CVE-2022-36071, GHSA-54qx-8p8w-xhg8
Record: https://patchnext.com/advisories/cve-2022-36071 (revision 1, source checked 26 Oct 2026, 14:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/drakkan/sftpgo/v2 2.3.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/drakkan/sftpgo/v2: affected >= 2.2.0, < 2.3.4; fixed in 2.3.4

## Suggested inspection (read-only)
- Go github.com/drakkan/sftpgo/v2: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/drakkan/sftpgo/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-54qx-8p8w-xhg8 (GitHub-reviewed advisory GHSA-54qx-8p8w-xhg8 lists affected ranges: Go github.com/drakkan/sftpgo/v2 >=2.2.0 <2.3.4)

Commands are suggestions: review each one before running it.