Is CVE-2026-50755 exploited in the wild?

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

How severe is CVE-2026-50755?

Informational severity, with a CVSS score of 9.1, 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-50755?

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-50755 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-50755?

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-50755: DayuanJiang next-ai-draw-io auth bypass via X-Forwarded-For spoofing

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

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-50755 attacked?

It is attacked over the network, in a web application.

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

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-50755 · Severity: info · CVSS 9.1 · Published 2026-07-21

next-ai-draw-io is a web application that integrates AI capabilities with diagramming tools. A security flaw allows remote attackers to forge user identities by manipulating network headers. This can lead to unauthorized use of expensive AI resources at the owner's expense, bypass of usage limits, and the ability to impersonate other users' activity logs.

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

Quick answers

Is CVE-2026-50755 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-50755 being exploited in the wild.
How severe is CVE-2026-50755?: Informational severity, with a CVSS score of 9.1, 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-50755?: 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-50755 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-50755?: 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

The vulnerability exists in the identity generation logic within `lib/user-id.ts`. The application derives the `userId` exclusively from the client-provided `X-Forwarded-For` HTTP header without verifying if the request passed through a trusted reverse proxy. Because this header is entirely client-controlled, an unauthenticated attacker can rotate header values to bypass DynamoDB-based quota enforcement (rate limiting) and impersonate other users by spoofing their IP addresses. This forged identity is also used for telemetry tracking in Langfuse and token usage accounting, leading to data corruption and potential financial exhaustion of the operator's AI API keys.

Affected products

DayuanJiang next-ai-draw-io <= 0.4.13

Timeline

2026-03-16: other: Vulnerability discovered
2026-03-17: disclosed: Initial disclosure to vendor via GitHub issue
2026-07-21: advisory: CVE published

References

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