Skip to content
Fencer Vulns
high 7.1

CVE-2021-32726 json

Webauthn tokens not removed after user has been deleted

published 2021-07-12 5 y ago modified 2026-06-17 4 mo ago also EUVD-2021-19508

cvss
7.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.8%
EPSS 1.8% chance of exploitation in 30 days, percentile 78%
public exploits
0
none known

Summary

Nextcloud Server is a Nextcloud package that handles data storage. In versions prior to 19.0.13, 20.011, and 21.0.3, webauthn tokens were not deleted after a user has been deleted. If a victim reused an earlier used username, the previous user could gain access to their account. The issue was fixed in versions 19.0.13, 20.0.11, and 21.0.3. There are no known workarounds.

Patch / fix

  • nextcloud nextcloud_server 19.0.13, 20.0.11, 21.0.3
  • nextcloud Package Hub 15 SP3, Package Hub 15 SP2, Package Hub 15 SP1 +3 more 20.0.11-bp153.2.3.1

opensuse advisories openSUSE-SU-2021:1068-1

  • nextcloud Arch Linux 21.0.3-1

arch linux advisories AVG-2144

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2021-32726 updated cvss 9.1

nextcloud: server security bypass

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.78% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected products

  • nextcloud security-advisories

Classification

Weakness
  • CWE-708 Incorrect Ownership Assignment
  • CWE-287 Improper Authentication

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.