Skip to main content
VulnerabilityPublished

CVE-2026-63373: jgraph drawio · Cross-Site Request Forgery (CSRF)

Affects jgraph drawioSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.2 Medium : upgrade to 30.2.7 when convenient.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 3.1 base score
4.2Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 30.2.7
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Sep 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 5 Nov 2026.

What to do

Upgrade drawio and jgraph/drawio to 30.2.7.

Affected software

ProductAffectedFixed in
jgraphdrawioAffected
  • <30.2.7
Fixed in
  • 30.2.7
GitHubjgraph/drawiopkg:github/jgraph/drawioOther threatsAffected
  • <30.2.7
Fixed in
  • 30.2.7

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

AI-suggested

Upgrade draw.io to version 30.2.7 or later, where this vulnerability is fixed. The fix ensures proper validation of stateToken and cookieToken in the OAuth callback handler to prevent CSRF attacks. No other mitigation is indicated by the vendor advisory.

Description

draw.io is a configurable diagramming and whiteboarding application. Prior to version 30.2.7, the OAuth callback handler in src/main/java/com/mxgraph/online/AbsAuth.java skips comparison of stateToken and cookieToken whenever IS_GAE is false, which affects self-hosted Docker and WAR deployments. An attacker can provide an authorization code for the attacker's cloud-storage identity and induce a victim to visit a callback URL, causing the victim's draw.io session to become authenticated as the attacker identity without a valid state binding. The shared handler affects Google Drive, OneDrive, GitHub, GitLab, and Dropbox integrations. The victim can then unknowingly perform cloud-storage actions under the attacker's identity, causing session integrity loss and misattribution, but the identity binding does not itself grant access to existing victim cloud files. This issue is fixed in version 30.2.7.

References

Community reviews

Loading reviews…