{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-82411 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-82411 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-82411 is a medium-severity vulnerability in maykinmedia open-object, published on 28 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-82411 and fix it if it is affected.\n\nWhat it is: CVE-2026-82411 is a medium-severity vulnerability in maykinmedia open-object, published on 28 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-82411 in the wild and no public exploit code.\n\nAffected product: maykinmedia open-object. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-82411/ (Markdown: https://insights.sbomify.com/CVE-2026-82411/index.md)","id":"CVE-2026-82411","markdown":"https://insights.sbomify.com/CVE-2026-82411/index.md","name":"CVE-2026-82411","record":{"aliases":["GHSA-55w6-rqp5-j5wx"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Objects API: Cross-object-type authorization bypass on the object history-detail endpoint","id":"CVE-2026-82411","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":9,"next":{"headline":"ntopng: Remote Code Execution via OS Command Injection in Vulnerability-Scan REST API","id":"CVE-2026-82412"},"packages":[],"prev":{"headline":"Pocketbase: Unhandled panic in worker goroutines","id":"CVE-2026-82410"},"products":["open-object"],"published":"2026-10-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-29","vendors":["maykinmedia"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-82411/"}