CVE-2026-45690

Nextcloud: Two-Factor Authentication Bypass via Pending Session Token Replay

MEDIUM

5.9

CVSS Score

Published: June 1, 2026 at 05:08 PM UTC

Updated: July 22, 2026 at 08:27 AM UTC

1 product affected across 1 vendorNextcloud/server

Using security-advisories by nextcloud?

Get instant alerts when new vulnerabilities affect security-advisories - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.9

Exploit prediction

EPSS 0.3%

SSVC

No known exploit

Description

Nextcloud is an open source content collaboration platform. In Nextcloud Server from versions 32.0.0 to before 32.0.9, and 33.0.0 to before 33.0.3, an authentication bypass vulnerability allowed attackers with knowledge of a user's password to circumvent two-factor authentication (2FA) protections. When a user initiated login with valid credentials on a 2FA-enabled account, the system created a temporary session token before enforcing the second factor challenge. This token could be extracted and replayed via HTTP Basic Authentication to gain unauthorized access to authenticated endpoints. It is recommended that the Nextcloud Server is upgraded to 33.0.3 or 32.0.9. It is recommended that the Nextcloud Enterprise Server is upgraded to 33.0.3, 32.0.9, 31.0.14.5, 30.0.17.9 or 29.0.16.16

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Nextcloud/server · Nextcloudnextcloud-app

95%

29.0.0 ≤ v < 29.0.16.1630.0.0 ≤ v < 30.0.17.931.0.0 ≤ v < 31.0.14.532.0.0 ≤ v < 32.0.933.0.0 ≤ v < 33.0.3

Affected range stops below 29.0.16.16, so it looks safe — our inference, not a vendor statement

Affected range stops below 30.0.17.9, so it looks safe — our inference, not a vendor statement

Affected range stops below 31.0.14.5, so it looks safe — our inference, not a vendor statement

Affected range stops below 32.0.9, so it looks safe — our inference, not a vendor statement

Affected range stops below 33.0.3, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (3)

x_refsource_CONFIRMVendor Advisory

Source: cverecord

https://github.com/nextcloud/security-advisories/security/advisories/GHSA-jgcj-v42r-9922

x_refsource_MISCIssue TrackingPatch

Source: cverecord

https://github.com/nextcloud/server/pull/59758

x_refsource_MISCPermissions Required

Source: cverecord

https://hackerone.com/reports/3639301

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.9MEDIUMGitHub_M

Attack Vector: NETWORK
Complexity: HIGH
Privileges: LOW
User Interaction: NONE
Scope: UNCHANGED
Confidentiality: LOW
Integrity: HIGH
Availability: NONE

Vector?

Quick Info

StatusANALYZED

CWE

CWE-287

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card