# CVE-2026-54657: Missing authorization in open-zaak

> Attackers with valid tokens can retrieve unauthorized case or document metadata due to missing authorization filtering in search endpoints.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-f29q-7rpr-jmjx

## What is CVE-2026-54657?

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.

### Official 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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2026-54657?


## How do I fix CVE-2026-54657?

No fix has been published for CVE-2026-54657 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-54657 being exploited?

There is no known exploitation of CVE-2026-54657 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54657 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2026-54657 in the wild and no public exploit code.

Affected product: open-zaak. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54657/ (Markdown: https://insights.sbomify.com/CVE-2026-54657/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54657
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54657
- OSV: https://osv.dev/vulnerability/CVE-2026-54657

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54657/
Summaries are generated and may contain mistakes; the official description above is the record.