CVE-2026-82411

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (23rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-112551 (ENISA EUVD)Source: ENISA EUVD

6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.5Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

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.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
23rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 28, 2026

Last Modified

October 29, 2026

Advisory Details (9)

Auto-updated Oct 29, 2026
🔬 Proof of concept available. Fix named in the CVE record. Sources: github_commit, github.
Web page

GitHub - maykinmedia/open-object at 4.1.1 · GitHub

https://github.com/maykinmedia/open-object/tree/4.1.1
Web page

GitHub - maykinmedia/open-object at 4.0.2 · GitHub

https://github.com/maykinmedia/open-object/tree/4.0.2
Web page

GitHub - maykinmedia/open-object at 3.6.2 · GitHub

https://github.com/maykinmedia/open-object/tree/3.6.2
Web page

GitHub - maykinmedia/open-object at 2.5.1 · GitHub

https://github.com/maykinmedia/open-object/tree/2.5.1
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Cross-object-type authorization bypass on object history-detail endpoint (Objects API) — IDOR · Advisory · maykinmedia/open-object · GitHub

https://github.com/maykinmedia/open-object/security/advisories/GHSA-55w6-rqp5-j5wx
GitHub commit

commit ce6b1820619c (maykinmedia/open-object)

Fix landed in maykinmedia/open-object commit ce6b1820619c — awaiting tagged release

https://github.com/maykinmedia/open-object/commit/ce6b1820619c843748bc5231597aa7fc060d95fe
GitHub commit

commit 6154d9c2ed8c (maykinmedia/open-object)

Fix landed in maykinmedia/open-object commit 6154d9c2ed8c — awaiting tagged release

https://github.com/maykinmedia/open-object/commit/6154d9c2ed8c162b61f2d42db2de4eda5081347f
GitHub commit

commit 27e806eff04c (maykinmedia/open-object)

Fix landed in maykinmedia/open-object commit 27e806eff04c — awaiting tagged release

https://github.com/maykinmedia/open-object/commit/27e806eff04c52ebe1e78126c288b63fc0308b52
GitHub commit

commit 11c5b85ea5d1 (maykinmedia/open-object)

Fix landed in maykinmedia/open-object commit 11c5b85ea5d1 — awaiting tagged release

https://github.com/maykinmedia/open-object/commit/11c5b85ea5d1d80f940883f01b8b8ea80ccdd47c

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 10× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  3. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  4. 2026-10-29 18:27 UTCEG score recompute
  5. 2026-10-29 17:27 UTCEG score recompute
  6. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  7. 2026-10-28 23:26 UTCEG score recompute
  8. 2026-10-28 23:01 UTCENISA EUVD ID recordedEUVD-2026-112551 · Source: ENISA EUVD
  9. 2026-10-28 22:48 UTCEG score recomputeFirst assessed: 6.5 MEDIUM
  10. 2026-10-28 22:48 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-82411?
CVE-2026-82411 is a medium-severity vulnerability; its CVE record was published on October 28, 2026. 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…
When was the CVE record for CVE-2026-82411 published?
The CVE record for CVE-2026-82411 was published on October 28, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 29, 2026; the record at its source may have been updated since.
Is CVE-2026-82411 actively exploited?
CVE-2026-82411 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-82411?
CVE-2026-82411 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-82411?
The CVE record for CVE-2026-82411 names the fix: "This issue is fixed in versions 2.5.1, 3.6.2, 4.0.2, and 4.1.1."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-82411

Explore →

Is Your Infrastructure Affected by CVE-2026-82411?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs