{"answers":{"affected":"1 open source package ship an affected version, including nextcloud.","exploited":"There is no known exploitation of CVE-2026-45157 in the wild and no public exploit code.","fix":"Upgrade nextcloud to a fixed version for your release line: 32.0.9 or 33.0.3.","what":"CVE-2026-45157 is a medium-severity missing authorization vulnerability in nextcloud security-advisories, published on 1 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-45157 and fix it if it is affected.\n\nWhat it is: CVE-2026-45157 is a medium-severity missing authorization vulnerability in nextcloud security-advisories, published on 1 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-45157 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nextcloud (Bitnami): affected from 32.0.0; fixed in 32.0.9, 33.0.3\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-45157/ (Markdown: https://insights.sbomify.com/CVE-2026-45157/index.md)","id":"CVE-2026-45157","markdown":"https://insights.sbomify.com/CVE-2026-45157/index.md","name":"CVE-2026-45157","record":{"aliases":["BIT-nextcloud-2026-45157","GHSA-45pj-p7x7-4mhc"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Nextcloud Server","requires_auth":"low_privilege","summary":"Attackers with valid share tokens can access temporary upload files of the share owner, exposing sensitive data during ongoing uploads.","user_interaction":"required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"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, 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","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Nextcloud: Valid share tokens allow to access tempory upload files of share owner","id":"CVE-2026-45157","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":1,"n_references":3,"next":{"headline":"OPNsense: Command Injection via Attacker-Controlled DHCP Config","id":"CVE-2026-45158"},"packages":[{"ecosystem":"Bitnami","fixed":["32.0.9","33.0.3"],"introduced":["32.0.0","33.0.0"],"last_affected":[],"package":"nextcloud","purl":"pkg:bitnami/nextcloud","source":"BIT-nextcloud-2026-45157"}],"prev":{"headline":"Nextcloud: Authentication Bypass in ID4me handling via Missing JWT Signature Verification in User OIDC","id":"CVE-2026-45156"},"products":["security-advisories"],"published":"2026-06-01","related":[],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-01","vendors":["nextcloud"]},"summary":"Attackers with valid share tokens can access temporary upload files of the share owner, exposing sensitive data during ongoing uploads.","url":"https://insights.sbomify.com/CVE-2026-45157/"}