CVE-2026-55551

ZAC: Missing per-zaaktype authorization on by-ID decision and process reads

Published Oct 30, 2026 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
Description
ZAC is an open-source, workflow-based Common Ground component for Dutch municipal case management. Prior to 5.2.0, by-id read endpoints in `src/main/kotlin/nl/info/zac/app/zaak/ZaakRestService.kt` omit `assertPolicy`(`policyService.readZaakRechten(zaak).lezen`) authorization. `RequestAuthorizationFilter` and `hasAnyApplicationRole` require only an application role on any zaaktype, not the target case's type, while `zaak-rechten.rego` enforces the actual `zaaktype_allowed` boundary only when invoked. An authenticated low-privileged municipal user who knows a case or decision UUID can use `GET /rest/zaken/besluit/zaakUuid/{uuid}` (`listBesluitenForZaakUUID`) to read decisions including types, dates, and free-text toelichting; `GET /rest/zaken/besluit/{uuid}/historie` (`listBesluitHistorie`) to read audit old/new values; and `GET /rest/zaken/{uuid}/process-diagram` (`downloadProcessDiagram`) to read BPMN workflow state across unauthorized zaaktypes. The advisory also identifies `zaak/{uuid}/afzender` (`listAfzendersVoorZaak`) as exposing zaaktype mailbox configuration without a policy check. The search/_zoek path is correctly authorization-filtered and is not part of this by-id read cluster. This issue is fixed in version 5.2.0.

Analysis

AI-generated

Technical impact

The vulnerability in the ZAC component allows an authenticated municipal user with a low‑privileged role to retrieve sensitive case and decision data by directly using UUIDs. Because the read endpoints omit the necessary per‑zaaktype authorization checks, a user can pull decision details, histories, and BPMN process diagrams for any case they know the identifier of, thereby exposing dates, free‑text explanations, audit logs and even mailbox configurations that belong to other zaaktypes. This constitutes an information disclosure breach that could be leveraged to gather operational insights about other cases or identify systemic weaknesses.

Affected Systems

The issue affects the Infonl Dimpact Zaakafhandelcomponent before version 5.2.0. Any deployment of that open‑source package that has not been updated to the 5.2.0 release is vulnerable. The simplest scope is all 5.x releases older than 5.2.0, which includes the current stable 5.1.x series.

Risk and Exploitability

The CVSS score of 6.5 indicates a medium severity. EPSS is not available, but the vulnerability is not listed in CISA KEV, suggesting limited public exploitation. Attackers needing only to possess a valid user session and a case UUID can exploit these endpoints, so the primary attack vector is authenticated misuse via the API. The risk is mitigated by patching, as no remote code execution or privilege escalation beyond read access is possible.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the Dimpact Zaakafhandelcomponent to release version 5.2.0 or newer.
  • Restart the application to ensure the updated code is active and old API routes are refreshed.
  • Configure API gateway or firewall rules to restrict access to the affected endpoints for low‑privileged user roles, reducing the attack surface while the patch is deployed.

Generated by OpenCVE AI on October 30, 2026 at 19:48 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Infonl
Infonl dimpact-zaakafhandelcomponent
Vendors & Products Infonl
Infonl dimpact-zaakafhandelcomponent
Type Values Removed Values Added
Description ZAC is an open-source, workflow-based Common Ground component for Dutch municipal case management. Prior to 5.2.0, by-id read endpoints in `src/main/kotlin/nl/info/zac/app/zaak/ZaakRestService.kt` omit `assertPolicy`(`policyService.readZaakRechten(zaak).lezen`) authorization. `RequestAuthorizationFilter` and `hasAnyApplicationRole` require only an application role on any zaaktype, not the target case's type, while `zaak-rechten.rego` enforces the actual `zaaktype_allowed` boundary only when invoked. An authenticated low-privileged municipal user who knows a case or decision UUID can use `GET /rest/zaken/besluit/zaakUuid/{uuid}` (`listBesluitenForZaakUUID`) to read decisions including types, dates, and free-text toelichting; `GET /rest/zaken/besluit/{uuid}/historie` (`listBesluitHistorie`) to read audit old/new values; and `GET /rest/zaken/{uuid}/process-diagram` (`downloadProcessDiagram`) to read BPMN workflow state across unauthorized zaaktypes. The advisory also identifies `zaak/{uuid}/afzender` (`listAfzendersVoorZaak`) as exposing zaaktype mailbox configuration without a policy check. The search/_zoek path is correctly authorization-filtered and is not part of this by-id read cluster. This issue is fixed in version 5.2.0.
Title ZAC: Missing per-zaaktype authorization on by-ID decision and process reads
Weaknesses CWE-285
CWE-639
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}

Weaknesses
  • CWE-285

    Improper Authorization

  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 6, 2026, 4:26 PM
Reserved
Jun 16, 2026, 11:01 PM
Status
Deferred
Published
Oct 30, 2026, 5:17 PM
Modified
Nov 6, 2026, 5:18 PM