{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-54657 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-54657 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-54657 is a medium-severity missing authorization vulnerability in open-zaak, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-54657 and fix it if it is affected.\n\nWhat it is: CVE-2026-54657 is a medium-severity missing authorization vulnerability in open-zaak, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-54657 in the wild and no public exploit code.\n\nAffected product: open-zaak. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-54657/ (Markdown: https://insights.sbomify.com/CVE-2026-54657/index.md)","id":"CVE-2026-54657","markdown":"https://insights.sbomify.com/CVE-2026-54657/index.md","name":"CVE-2026-54657","record":{"aliases":["GHSA-f29q-7rpr-jmjx"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Open Zaak data layer","requires_auth":"low_privilege","summary":"Attackers with valid tokens can retrieve unauthorized case or document metadata due to missing authorization filtering in search endpoints.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"},{"id":"CWE-285","name":"Improper Authorization"}],"description":"Open Zaak is an open-source data and services layer for Dutch case-oriented working. From 1.0.0 until 1.27.2, 1.28.2, and 1.29.0, the POST search endpoints /zaken/api/v1/zaken/_zoek and /documenten/api/v1/enkelvoudiginformatieobjecten/_zoek do not filter result querysets according to the authorizations associated with the request token. A caller with a valid zaken.lezen or documenten.lezen token can therefore retrieve case or document metadata outside the token's authorized types or confidentiality levels. Document searches require known UUIDs, and document content remains protected by separate download authorization. This issue is fixed in versions 1.27.2, 1.28.2, and 1.29.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Missing authorization in open-zaak","id":"CVE-2026-54657","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"@hypequery/clickhouse has SQL Injection in parameter escaping that allows arbitrary SQL execution","id":"CVE-2026-54658"},"packages":[],"prev":{"headline":"`datamodel-code-generator` vulnerable to code execution on import via unescaped `validators` entries in --extra-template-data","id":"CVE-2026-54656"},"products":["open-zaak"],"published":"2026-10-16","related":[],"sources":[{"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-10-16","vendors":["open-zaak"]},"summary":"Attackers with valid tokens can retrieve unauthorized case or document metadata due to missing authorization filtering in search endpoints.","url":"https://insights.sbomify.com/CVE-2026-54657/"}