Live › vulnerability › CVE-2026-55836
Go to dashboardOpen Zaak's document import task does not confine the bestandspad path in uploaded CSV rows to the configured import directory. A client with an all-authorizations application token can point it at any file the Celery worker can read, and the worker copies that file into document storage where it can be downloaded.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Deployments running Open Zaak versions from 1.13.0 up to 1.27.2, 1.28.2, or 1.29.0 that use the document CSV import feature are exposed. The attacker needs a client application token with all authorizations, so deployments that only issue narrow tokens are less exposed. Installations on the fixed versions are not affected.
No product ranges from the sources yet.
1.27.2, 1.28.2, or 1.29.0, matching your release line.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Open Zaak is an open-source data and services layer for Dutch case-oriented working. From 1.13.0 until 1.27.2, 1.28.2, and 1.29.0, _import_document_row in src/openzaak/components/documenten/tasks.py uses the attacker-controlled bestandspad CSV field without ensuring that the resolved path remains under IMPORT_DOCUMENTEN_BASE_DIR. A client with an all-authorizations application token can supply an absolute or parent-traversal path to a file readable by the Celery service account. The worker copies that file into document storage, allowing its contents to be retrieved through the normal document download API and exposing server secrets or other private files. This issue is fixed in versions 1.27.2, 1.28.2, and 1.29.0.
This page as .md · .json · in your agent: get_signal("CVE-2026-55836")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.