Is CVE-2026-50756 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-50756 being exploited in the wild.

How severe is CVE-2026-50756?

Informational severity, with a CVSS score of 7.5, published 21 July 2026.

Which products and versions are affected?

DayuanJiang Next-Ai-Draw-Io <= 0.4.13.

Is there a fix for CVE-2026-50756?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-50756 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-50756?

Check whether you run DayuanJiang Next-Ai-Draw-Io at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-50756: DayuanJiang next-ai-draw-io SSRF guard bypass in x-ai-provider

Q: Is there a fix for CVE-2026-50756?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

Q: How is CVE-2026-50756 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-50756?

Check whether you run DayuanJiang Next-Ai-Draw-Io at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-50756 · Severity: info · CVSS 7.5 · Published 2026-07-21

A security flaw in the next-ai-draw-io application allows unauthorized individuals to intercept sensitive information. By manipulating how the application connects to AI services, an attacker can trick the server into sending private conversation history, diagram data, and internal system instructions to a server they control. This could lead to the exposure of proprietary business logic and confidential user designs.

Technologies: DayuanJiang Next-Ai-Draw-Io. Vendors: DayuanJiang.

Quick answers

Is CVE-2026-50756 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-50756 being exploited in the wild.
How severe is CVE-2026-50756?: Informational severity, with a CVSS score of 7.5, published 21 July 2026.
Which products and versions are affected?: DayuanJiang Next-Ai-Draw-Io <= 0.4.13.
Is there a fix for CVE-2026-50756?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-50756 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-50756?: Check whether you run DayuanJiang Next-Ai-Draw-Io at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A Server-Side Request Forgery (SSRF) vulnerability exists in next-ai-draw-io version 0.4.13 and earlier due to an incomplete fix for a previous SSRF issue (GHSA-9qf7-mprq-9qgm). The application's SSRF guard in `lib/ai-providers.ts` explicitly exempts the 'edgeone' and 'ollama' providers from requiring an API key when a custom `baseUrl` is provided. By supplying the `x-ai-provider: edgeone` and `x-ai-base-url` headers, a remote unauthenticated attacker can redirect server-side AI API calls to an arbitrary endpoint. This results in the server sending a POST request containing the full AI system prompt (approx. 18KB), user conversation history, and diagram XML to the attacker-controlled server.

Affected products

DayuanJiang next-ai-draw-io <= 0.4.13

Timeline

2026-03-17: disclosed: Vulnerability discovered and reported to vendor via GitHub issue.
2026-07-21: advisory: CVE-2026-50756 published.

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.