CVE-2026-82411
Last modified
CVE-2026-82411 is a medium-severity vulnerability rated 6.5/10 on the CVSS scale. 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}`. EPSS estimates a 0.31% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| maykinmedia | open-object | >= 2.4.3, < 2.5.1; >= 3.0.0, < 3.6.2; >= 4.0.0-rc.1, < 4.0.2; >= 4.1.0, < 4.1.1 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-82411?
How severe is CVE-2026-82411?
How do I fix CVE-2026-82411?
How Strix Helps
- Uncovering a hidden BOLA in Appsmith's snapshot logicStrix autonomously discovered a BOLA/IDOR vulnerability in Appsmith's snapshot deletion path.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-82405Klever-Go is the Go implementation of the Klever blockchain …8.7
- CVE-2026-82406Klever-Go is the Go implementation of the Klever blockchain …7.1
- CVE-2026-82407Klever-Go is the Go implementation of the Klever blockchain …7
- CVE-2026-82409Klever-Go is the Go implementation of the Klever blockchain …8.4
- CVE-2026-8241A vulnerability has been found in Industrial Application Sof…5.5
- CVE-2026-82410Pocketbase is an open source web backend written in go. Prio…8.7
- CVE-2026-82412ntopng is a web-based network traffic monitoring application…8.8
- CVE-2026-82416FrankenPHP is a modern application server for PHP. Prior to …7.7
- CVE-2026-82417### Summary `qs.stringify` throws a `TypeError` when it s…5.3
- CVE-2026-82418IBM Watson Speech Services Cartridge 4.0.0 through 5.4.0 cou…9.8
- CVE-2026-8242A vulnerability was found in Industrial Application Software…3.7
- CVE-2026-82421A vulnerability was identified in itsourcecode Sales and Inv…6.3
Are you affected by CVE-2026-82411?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
