CVE-2026-82411

{"id": "CVE-2026-82411", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-82411", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-10-29T15:30:00.984556Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 6.5, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 3.6, "exploitabilityScore": 2.8}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "maykinmedia", "product": "open-object", "versions": [{"status": "affected", "version": ">= 2.4.3, < 2.5.1"}, {"status": "affected", "version": ">= 3.0.0, < 3.6.2"}, {"status": "affected", "version": ">= 4.0.0-rc.1, < 4.0.2"}, {"status": "affected", "version": ">= 4.1.0, < 4.1.1"}]}]}], "published": "2026-10-28T23:17:10.930", "references": [{"url": "https://github.com/maykinmedia/open-object/commit/11c5b85ea5d1d80f940883f01b8b8ea80ccdd47c", "source": "security-advisories@github.com"}, {"url": "https://github.com/maykinmedia/open-object/commit/27e806eff04c52ebe1e78126c288b63fc0308b52", "source": "security-advisories@github.com"}, {"url": "https://github.com/maykinmedia/open-object/commit/6154d9c2ed8c162b61f2d42db2de4eda5081347f", "source": "security-advisories@github.com"}, {"url": "https://github.com/maykinmedia/open-object/commit/ce6b1820619c843748bc5231597aa7fc060d95fe", "source": "security-advisories@github.com"}, {"url": "https://github.com/maykinmedia/open-object/security/advisories/GHSA-55w6-rqp5-j5wx", "source": "security-advisories@github.com"}, {"url": "https://github.com/maykinmedia/open-object/tree/2.5.1", "source": "security-advisories@github.com"}, {"url": "https://github.com/maykinmedia/open-object/tree/3.6.2", "source": "security-advisories@github.com"}, {"url": "https://github.com/maykinmedia/open-object/tree/4.0.2", "source": "security-advisories@github.com"}, {"url": "https://github.com/maykinmedia/open-object/tree/4.1.1", "source": "security-advisories@github.com"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-639"}]}], "descriptions": [{"lang": "en", "value": "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."}], "lastModified": "2026-10-29T18:17:35.220", "sourceIdentifier": "security-advisories@github.com"}