VulnerabilityPublished 28 Oct 2026

CVE-2026-82411: maykinmedia open-object · Insecure Direct Object Reference

Affects maykinmedia open-objectSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium · fixed in 4.1.1 : update maykinmedia open-object when convenient.

Data as of 28 Oct 2026, 23:12 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 4.1.1, 4.0.2, 3.6.2 +1

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade open-object and maykinmedia/open-object to 4.1.1, 4.0.2, 3.6.2 or 2.5.1.

Affected software

Product	Affected	Fixed in
maykinmediaopen-object	Affected >=4.1.0 <4.1.1	Fixed in 4.1.1
maykinmediaopen-object	Affected >=4.0.0-rc.1 <4.0.2	Fixed in 4.0.2
maykinmediaopen-object	Affected >=3.0.0 <3.6.2	Fixed in 3.6.2
maykinmediaopen-object	Affected >=2.4.3 <2.5.1	Fixed in 2.5.1
GitHubmaykinmedia/open-object`pkg:github/maykinmedia/open-object`Other threats	Affected >=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	Fixed in 2.5.1 3.6.2 4.0.2 4.1.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability is fixed in open-object versions 2.5.1, 3.6.2, 4.0.2, and 4.1.1. Users should upgrade to one of these fixed versions to remediate the issue. There is no indication of any temporary workaround or that the issue is already mitigated without patching. No additional mitigation steps beyond upgrading are specified.

Description

A vulnerability in maykinmedia's open-object API versions 2.4.3 to before 2.5.1, 3.0.0 to before 3.6.2, 4.0.0-rc.1 to before 4.0.2, and 4.1.0 to before 4.1.1 allows an API token scoped to read one ObjectType to access full versioned records of objects of other ObjectTypes via the history-detail endpoint. This bypasses authorization checks that normally restrict access, potentially exposing sensitive data such as citizen or case records in government deployments. The issue is fixed in versions 2.5.1, 3.6.2, 4.0.2, and 4.1.1.

Impact

An attacker with any valid non-superuser API token scoped to read one ObjectType can access complete versioned records of objects from other ObjectTypes via the history-detail API endpoint. This unauthorized data disclosure can include sensitive information such as citizen or case records, which is particularly critical in government deployments. The vulnerability does not allow modification or deletion, only read access. The CVSS 3.1 base score is 6.5 (medium severity) reflecting network attack vector, low complexity, low privileges required, no user interaction, unchanged scope, high confidentiality impact, no integrity or availability impact.

Summary

Open Object's API and admin interface have an authorization bypass vulnerability (CWE-639) affecting versions >=2.4.3 <2.5.1, >=3.0.0 <3.6.2, >=4.0.0-rc.1 <4.0.2, and >=4.1.0 <4.1.1. The vulnerability arises because the history-detail endpoint (`GET /api/v2/objects/{uuid}/{index}`) calls `get_queryset()` and `get_object_or_404` directly, bypassing `check_object_permissions` and per-object permission checks in `ObjectTypeBasedPermission.has_object_permission`. The token's scope filtering applies only to list and search actions, not to this endpoint. Consequently, any valid non-superuser API token with read access to one ObjectType can retrieve full versioned records of objects from other ObjectTypes, including sensitive data. The normal retrieve endpoint correctly returns 403 for unauthorized access, and the sibling history action enforces grants properly. The issue is resolved in versions 2.5.1, 3.6.2, 4.0.2, and 4.1.1.

CWE-639Authorization Bypass Through User-Controlled Key (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #24OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
Architecture and Design
For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
Architecture and Design · Implementation
Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
Architecture and Design
Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.
OWASP Cheat Sheets
Access Control (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Insecure Direct Object Reference Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V4.1.2 (opens in a new tab)
V4.2.1 (opens in a new tab)
V8.3.8 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Oct 2026, 22:59 UTC

WeaknessesCWE-639

Technical details

References

Community reviews

Related threats