CVE-2026-63334: draw.io: SSRF via DNS rebinding in ProxyServlet bypasses private IP blocklist

Published Sep 21, 2026
·
Updated

draw.io is a configurable diagramming and whiteboarding application. Prior to version 30.2.7, deployments with ENABLEDRAWIOPROXY=1 are vulnerable to server-side request forgery because src/main/java/com/mxgraph/online/Utils.java performs the private-address check in Utils.sanitizeUrl() using one DNS resolution, while src/main/java/com/mxgraph/online/ProxyServlet.java later calls URL.openConnection() and performs a second resolution. An attacker-controlled hostname can resolve to a public address during validation and then to a private, link-local, or cloud metadata address when the connection is opened. Successful exploitation can return cloud instance metadata or responses from internal HTTP services through the proxy. This issue is fixed in version 30.2.7.

Affected Software

1 affected component
draw.io draw.io<30.2.7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade draw.io to a version that resolves this vulnerability.

    Fixed in 30.2.7

Event History

Sep 21, 2026
CVE Published
via MITRE·04:22 PM
Data Sourced
via MITRE·04:22 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed?

Deployments that set ENABLE_DRAWIO_PROXY=1 are affected before version 30.2.7. The issue is in the proxy path, where hostname validation and the outbound connection use separate DNS resolutions.

2

What does an attacker need to exploit this?

An attacker needs to control a hostname whose DNS responses can change between the proxy's validation lookup and its connection lookup. They can make it resolve publicly during validation and then resolve to a private, link-local, or cloud metadata address for the outbound request.

3

What can an attacker access through successful exploitation?

Successful exploitation can return responses from internal HTTP services or cloud instance metadata through the proxy. The reported impact is disclosure of confidential information.

4

What should be done if upgrading is not immediately possible?

Disable the draw.io proxy by ensuring ENABLE_DRAWIO_PROXY is not set to 1. This removes the affected proxy functionality described in the advisory.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203