Live › vulnerability › CVE-2026-82411
Go to dashboardA valid API token with read access to one ObjectType can fetch the full versioned record of objects belonging to other ObjectTypes through the history-detail endpoint. The authorization checks that the normal retrieve endpoint applies are skipped on that path, so the record data, which can include sensitive personal or case records, is disclosed.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 23:35 UTC. All times on this page are UTC.
Deployments of Open Object from 2.4.3 up to the fixed releases that issue non-superuser API tokens with a read grant on at least one ObjectType. Government or case-management deployments holding citizen or sensitive records are the highest-risk setups. Instances on the fixed versions, or where only superuser tokens exist, are not affected.
No product ranges from the sources yet.
GET /api/v2/objects/{uuid}/{index} that is reachable with non-superuser API tokens.2.5.1, 3.6.2, 4.0.2, or 4.1.1 depending on the release line in use.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Open Object provides an API and admin interface to manage objects and object types. From 2.4.3 until 2.5.1, 3.6.2, 4.0.2, and 4.1.1, a token scoped to read one ObjectType can read the full versioned record of an object of any other ObjectType via the history-detail endpoint GET /api/v2/objects/{uuid}/{index}. The history_detail action in src/objects/api/v2/views.py calls self.get_queryset() and get_object_or_404 directly instead of self.get_object(), so check_object_permissions and the per-object check in ObjectTypeBasedPermission.has_object_permission are not invoked. The queryset's filter_for_token applies only to the list and search actions, while ObjectTypeBasedPermission.has_permission allows non-create actions, leaving neither check to constrain history-detail records to the token's permitted ObjectType. The normal retrieve endpoint returns 403 for the same unauthorized object, and the sibling history action enforces the grant. Any valid non-superuser API token with a read grant on at least one ObjectType can therefore disclose another ObjectType's complete versioned object data, which can include citizen or case records and sensitive identifiers in government deployments. This issue is fixed in versions 2.5.1, 3.6.2, 4.0.2, and 4.1.1.
This page as .md · .json · in your agent: get_signal("CVE-2026-82411")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.