# CVE-2026-110718: TurboDocx html-to-docx through 1.23.1 SSRF via img src Remote Image Download

> Attackers can exploit a Server-Side Request Forgery vulnerability in the html-to-docx library to access internal network resources and cloud metadata via malicious image URLs.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/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:** 14 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-wh99-p86q-m852

## What is CVE-2026-110718?

CVE-2026-110718 is a high-severity server-side request forgery vulnerability in TurboDocx html-to-docx, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

TurboDocx html-to-docx through 1.23.1 contains a server-side request forgery vulnerability that allows attackers supplying HTML to make the server fetch internal URLs via img src attributes. Attackers can reference loopback, private, or cloud metadata addresses that bypass the loose isValidUrl() check, and read responses embedded in the generated DOCX word/media folder.

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

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


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

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

## Is CVE-2026-110718 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110718 is a high-severity server-side request forgery vulnerability in TurboDocx html-to-docx, published on 14 Oct 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-110718 exists.

Affected product: TurboDocx html-to-docx. 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-110718/ (Markdown: https://insights.sbomify.com/CVE-2026-110718/index.md)
```

## Sources

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

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