# CVE-2026-82411 — maykinmedia open-object

> As of 2026-10-29, CVE-2026-82411 is a MEDIUM-severity vulnerability in maykinmedia open-object, CVSS v3.1 6.5, EPSS 0.3% (23.3th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-82411 as of 2026-10-29; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-10-29

## What is CVE-2026-82411?

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.

The record classifies CVE-2026-82411 under weakness class [CWE-639](https://intel.threadlinqs.com/cwe/CWE-639). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs no user interaction, and has high impact on confidentiality. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 22 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 6.5 — MEDIUM (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **EPSS (FIRST):** 0.3% probability of exploitation in the next 30 days, higher than 23.3% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 4.2/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-10-28

## Is CVE-2026-82411 being exploited?

It currently carries a trending score of 36 in the Threadlinqs vulnerability feed.

## Affected products and versions

- **maykinmedia**: open-object

## How to fix CVE-2026-82411

No vendor patch reference has been recorded for CVE-2026-82411 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-82411

No threat campaign in the Threadlinqs corpus currently references CVE-2026-82411, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD, FIRST EPSS. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [github.com](https://github.com/maykinmedia/open-object/security/advisories/GHSA-55w6-rqp5-j5wx)

**Other references**

- [github.com](https://github.com/maykinmedia/open-object/commit/11c5b85ea5d1d80f940883f01b8b8ea80ccdd47c)
- [github.com (27e806eff04c52ebe1e78126c288b63fc0308b52)](https://github.com/maykinmedia/open-object/commit/27e806eff04c52ebe1e78126c288b63fc0308b52)
- [github.com (6154d9c2ed8c162b61f2d42db2de4eda5081347f)](https://github.com/maykinmedia/open-object/commit/6154d9c2ed8c162b61f2d42db2de4eda5081347f)
- [github.com (ce6b1820619c843748bc5231597aa7fc060d95fe)](https://github.com/maykinmedia/open-object/commit/ce6b1820619c843748bc5231597aa7fc060d95fe)
- [github.com (2.5)](https://github.com/maykinmedia/open-object/tree/2.5.1)

_Showing 6 of 9 recorded references._

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-82411
No Threadlinqs detection currently covers CVE-2026-82411; it is re-checked on every ingest.
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp
