CVE-2026-82411 json
Objects API: Cross-object-type authorization bypass on the object history-detail endpoint
published 2026-10-28 11 d ago modified 2026-10-29 10 d ago also EUVD-2026-112551
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 23%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 10 d ago
Exploit prediction
0.31% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected products
- maykinmedia open-object
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
References
- github.com /maykinmedia/open-object/commit/11c5b85ea5d1d80f940883f01b8b8ea80ccdd47c
- github.com /maykinmedia/open-object/commit/27e806eff04c52ebe1e78126c288b63fc0308b52
- github.com /maykinmedia/open-object/commit/6154d9c2ed8c162b61f2d42db2de4eda5081347f
- github.com /maykinmedia/open-object/commit/ce6b1820619c843748bc5231597aa7fc060d95fe
- github.com /maykinmedia/open-object/security/advisories/GHSA-55w6-rqp5-j5wx
- github.com /maykinmedia/open-object/tree/2.5.1
- github.com /maykinmedia/open-object/tree/3.6.2
- github.com /maykinmedia/open-object/tree/4.0.2
- github.com /maykinmedia/open-object/tree/4.1.1
Sources
- CVE List CVE-2026-82411
- NVD CVE-2026-82411
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.