Vulnerability in nextcloud (CVE-2026-45157)
Summary
Vulnerability in nextcloud (CVE-2026-45157). Confidential information can be exposed externally. Mitigation: upgrade to 32.0.9, 33.0.3 or later.
Original description
The description as published by the source.
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, when a malicious user has access to a file share of a user, they could use this share token to also access the chunking upload directly and see temporary part files during on going uploads. It is recommended that the Nextcloud Server is upgraded to 32.0.9 or 33.0.3. It is recommended that the Nextcloud Enterprise Server is upgraded to 26.0.13.26, 27.1.11.25, 28.0.14.17, 29.0.16.16, 30.0.17.9, 31.0.14.5, 32.0.9 or 33.0.3
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-45157 has been found in nextcloud.
Confidential information can be exposed externally. CVSS score: 6.3/10.
What to do: upgrade nextcloud to 32.0.9, 33.0.3 or later.
If unsure, ask your IT team or search "nextcloud CVE-2026-45157" on the vendor's site.
CVE-2026-45157 (nextcloud) — CWE-284 / CVSS v3 6.3
Attack vector: remote (network-reachable)
Patched: 32.0.9, 33.0.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-284) exists in nextcloud.
Check the vendor advisory for the affected versions of nextcloud.
Severity: Medium (CVSS 6.3/10). Confidential information can be exposed externally.
Update to 32.0.9, 33.0.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'nextcloud' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'nextcloud' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
nextcloudを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade nextcloud to 32.0.9, 33.0.3ステージング環境で 32.0.9, 33.0.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- patch github.com
- web hackerone.com