CVE-2026-63416: draw.io: Path traversal in ExportProxyServlet allows access to arbitrary backend endpoints

Published Sep 21, 2026
·
Updated

draw.io is a configurable diagramming and whiteboarding application. Prior to version 30.2.7, src/main/java/com/mxgraph/online/ExportProxyServlet.java uses request.getPathInfo() to build a proxyPath and appends it directly to EXPORTURL without rejecting dot segments or confirming that the normalized destination remains under the configured export path. An unauthenticated request containing traversal segments can therefore address unintended routes on the internal export server, and the servlet forwards all request headers and the request body to that destination, allowing arbitrary header injection. Depending on the export service configuration, exploitation can expose administration, debugging, health, or configuration endpoints and can permit unintended internal actions. 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:18 PM
Data Sourced
via MITRE·04:18 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

An unauthenticated remote attacker can exploit it by sending a request containing traversal segments to the affected servlet. Exploitation depends on the attacker being able to reach the draw.io deployment over the network.

2

What determines the impact in a particular deployment?

Impact depends on the configuration and endpoints exposed by the internal export service. Traversal may provide access to administration, debugging, health, or configuration routes, and forwarded headers and request bodies may enable unintended internal actions.

3

Are default configurations known to be affected?

The available information describes this as affecting configurable draw.io deployments but does not state whether a default export-service configuration exposes sensitive routes. Review the configured export URL and the routes available on its backend.

4

What should be done if upgrading is not immediately possible?

Restrict network access to the affected draw.io servlet and to the internal export service, and limit the export service to only the routes required for normal operation. Ensure administrative, debugging, health, and configuration endpoints are not reachable through the export backend.

5

How can defenders identify potentially malicious requests?

Review requests to the ExportProxyServlet for path traversal dot segments in path information, especially requests attempting to reach unexpected export-backend routes. Also investigate requests carrying unusual headers or request bodies, since the servlet forwards both to the destination.

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