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


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-55w6-rqp5-j5wx

## What is CVE-2026-82411?

CVE-2026-82411 is a medium-severity vulnerability in maykinmedia open-object, published on 28 Oct 2026. 

### Official 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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-82411?


## How do I fix CVE-2026-82411?

No fix has been published for CVE-2026-82411 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-82411 being exploited?

There is no known exploitation of CVE-2026-82411 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-82411 and fix it if it is affected.

What it is: CVE-2026-82411 is a medium-severity vulnerability in maykinmedia open-object, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-82411 in the wild and no public exploit code.

Affected product: maykinmedia open-object. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-82411/ (Markdown: https://insights.sbomify.com/CVE-2026-82411/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-82411
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-82411
- OSV: https://osv.dev/vulnerability/CVE-2026-82411

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-82411/
Summaries are generated and may contain mistakes; the official description above is the record.