Skip to main content
VulnerabilityPublished

CVE-2026-65965: 3xpyth0n ideon · Improper Authorization

Affects 3xpyth0n ideonSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 0.9.4 soon.

Data as of 11 Nov 2026, 21:21 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.08.7
Patch
Available – fixed in 0.9.4
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 11 Nov 2026.

What to do

Upgrade 3xpyth0n ideon to 0.9.4.

Affected software

ProductAffectedFixed in
3xpyth0nideonAffected
  • <0.9.4
Fixed in
  • 0.9.4

AI-suggested

Upgrade ideon to version 0.9.4 or later, where the improper authorization vulnerability has been fixed. No additional mitigation steps are required as the patch fully addresses the issue.

Description

A vulnerability in ideon versions prior to 0.9.4 allows users with read-only viewer roles to perform unauthorized write operations on projects. Specifically, several project mutation endpoints under /api/projects/[id]/* do not enforce role-based access control, enabling viewers to modify or delete project content. The most critical endpoint affected is POST /api/projects/[id]/graph, which can delete and rewrite the entire project canvas. This flaw contradicts the intended read-only restriction for viewers and has been fixed in version 0.9.4.

References

Community reviews

Loading reviews…