CVE-2026-54657 open-zaak CVE debrief

Who should care

Defenders responsible for Open Zaak installations, administrators, and security teams should assess exposure and prioritize updates to prevent unauthorized access to sensitive information.

Why it matters

CVE-2026-54657 allows unauthorized access to case and document metadata in Open Zaak installations prior to versions 1.27.2, 1.28.2, and 1.29.0. Defenders should verify and update affected systems to prevent exposure.

• Potential unauthorized access to case and document metadata.
• Possible exposure of sensitive information outside authorized scopes.
• Need for verification of current Open Zaak versions and configurations.
• Prioritization of updates to fixed versions.

Technical summary

The Open Zaak search endpoints /zaken/_zoek and /enkelvoudiginformatieobjecten/_zoek do not properly filter results based on the authorizations linked to the request token. This vulnerability allows a caller with a valid token to retrieve metadata outside their authorized scope. Affected Open Zaak versions include those from 1.0.0 until 1.27.2, 1.28.2, and 1.29.0. Defenders should verify and update affected systems to prevent exposure. The vulnerability impacts case and document metadata access, potentially allowing unauthorized access to sensitive information.

Defensive priority

Defenders should prioritize verifying and updating Open Zaak installations to the fixed versions (1.27.2, 1.28.2, or 1.29.0) to prevent unauthorized access to case and document metadata.

Recommended defensive actions

• Verify Open Zaak installations and update to versions 1.27.2, 1.28.2, or 1.29.0.
• Review and adjust authorization configurations for search endpoints.
• Monitor for unusual activity or unauthorized access attempts.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.

Evidence notes

The CVE record and source item provide details on the vulnerability, affected versions, and fixed versions. However, the corpus does not establish exploitation or specific business impacts, requiring verification from official sources.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.