Skip to content
Fencer Intel
medium 4.6

CVE-2026-45153 json

Nextcloud: PIN bypass in PassCodeActivity via back button

published 5mo ago modified 3mo ago also BIT-nextcloud-2026-45153 , EUVD-2026-33672 , GHSA-2w7v-5299-3hw5

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

Summary

Nextcloud is an open source content collaboration platform. From version 33.0.0 to before version 33.1.0, after unlocking a locked Android phone the back-button could be used to bypass the Nextcloud Files app PIN. This issue has been patched in version 33.1.0.

Patch / fix

  • bitnami nextcloud 33.1.0
  • nextcloud nextcloud 33.1.0

Is CVE-2026-45153 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
5mo ago

Exploit prediction

0.15% chance of exploitation in the next 30 days, higher than 4% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 4.6 CVSS:3.1/AV:P/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N
OSV 3.1 4.6 CVSS:3.1/AV:P/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N

Affected packages

ecosystem package affected fixed in
bitnami nextcloud
>=33.0.0, <33.1.0
33.1.0

Affected products

  • nextcloud security-advisories

Classification

Weakness

References

Sources

Fencer Intel 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.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.