Read the docs

Missing user presence check in Nextcloud WebAuthn login

Priority LOW 38Published · Updated

Key facts

Attack vector
—
Privileges required
—
User interaction
—
Attack complexity
—
Impact type
—
Confidentiality · integrity · availability
—
Fix status
Fixed

No CVSS vector from any source. Fix status from GitHub.

Summary

Nextcloud Server before 20.0.13, before 21.0.5 and before 22.2.0 uses the webauthn-framework library version 3.3.1, which does not verify the user presence bit of WebAuthn assertions. An attacker can log in to a Nextcloud instance with an assertion generated by a YubiKey 5 NFC without pressing the button. The standard allows authenticators to skip the user presence test, but the relying party must check the bit.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

Description from the GitHub advisory

### Impact The PHP library webauthn-framework in version 3.3.1 as used by Nextcloud did not verify the user present bit of an WebAuthn assertion. An attacker is able to login into Nextcloud instances using an assertion generated by a YubiKey 5 NFC without pressing the button. According to the standard, authenticators are allowed to generate assertions without a test of user presence, however, a relying party is required to verify that the user present bit in an assertion is set. More details about the vulnerability details can be found on [fzi.de](https://www.fzi.de/en/news/news/detail-en/artikel/fsa-2021-1-fehlende-ueberpruefung-von-user-presence-in-webauthn-framework/) (FZI Research Center for Information Technology) and the vulnerability in the library is tracked as CVE-2021-38299. ### Patches It is recommended that the Nextcloud Server is upgraded to 20.0.13, 21.0.5 or 22.2.0. ### Workarounds None. ### References - [HackerOne](https://hackerone.com/reports/1178310) - [Pull Request](https://github.com/nextcloud/3rdparty/pull/780) ### For more information If you have any questions or comments about this advisory: * Create a post in [nextcloud/security-advisories](https://github.com/nextcloud/security-advisories/discussions) * Customers: Open a support ticket at [support.nextcloud.com](https://support.nextcloud.com)

Why it matters now

Fix Fixed Server (nextcloud): 20.0.13, 21.0.5, 22.2.0

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—Server (nextcloud)< 20.0.13, < 21.0.5 , < 22.2.020.0.13, 21.0.5, 22.2.0Patch availableGHSA-g36v-67gv-h757
  • Server (nextcloud) Vendor— Affected < 20.0.13, < 21.0.5 , < 22.2.0 Fixed in 20.0.13, 21.0.5, 22.2.0 Patch available GHSA-g36v-67gv-h757

Remediation

Upgrade Nextcloud Server to 20.0.13, 21.0.5 or 22.2.0.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

  • Fix · GHSA-g36v-67gv-h757 Server (nextcloud) Fixed in 20.0.13, 21.0.5, 22.2.0 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-g36v-67gv-h757

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences