# CVE-2026-72777: Next AI Draw.io 0.4.16 SSRF via DNS Rebinding in parse-url

> Unauthenticated attackers can exploit SSRF in Next AI Draw.io to access internal services and exfiltrate cloud metadata via DNS rebinding.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Aug 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-2f59-92g6-qm58

## What is CVE-2026-72777?

CVE-2026-72777 is a high-severity server-side request forgery vulnerability in DayuanJiang next-ai-draw-io, published on 13 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Next AI Draw.io through 0.4.16 contains a server-side request forgery vulnerability in the POST /api/parse-url endpoint due to hostname validation that only checks string patterns without DNS resolution. Unauthenticated attackers can supply hostnames that bypass string validation but resolve to internal addresses, allowing them to reach arbitrary internal HTTP services and exfiltrate responses including cloud metadata.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-72777?


## How do I fix CVE-2026-72777?

No fix has been published for CVE-2026-72777 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-72777 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72777 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72777 and fix it if it is affected.

What it is: CVE-2026-72777 is a high-severity server-side request forgery vulnerability in DayuanJiang next-ai-draw-io, published on 13 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72777 exists.

Affected product: DayuanJiang next-ai-draw-io. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72777/ (Markdown: https://insights.sbomify.com/CVE-2026-72777/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72777
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72777
- OSV: https://osv.dev/vulnerability/CVE-2026-72777

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72777/
Summaries are generated and may contain mistakes; the official description above is the record.