# CVE-2026-18647: jina-ai reader Crawler/Puppeteer crawler.ts isValidTLD server-side request forgery

> An attacker can exploit a flaw in the Crawler component to perform server-side request forgery, potentially accessing internal resources.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Aug 2026
- **Updated:** 4 Aug 2026
- **Also known as:** GHSA-4xp8-858j-g46w

## What is CVE-2026-18647?

CVE-2026-18647 is a medium-severity server-side request forgery vulnerability in jina-ai reader, published on 3 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A security vulnerability has been detected in jina-ai reader up to 1574bfd380d249c86c82db4dace0d9c8fe17e2b1. This issue affects the function isValidTLD of the file /backend/functions/src/cloud-functions/crawler.ts of the component Crawler/Puppeteer. The manipulation leads to server-side request forgery. Remote exploitation of the attack is possible. The exploit has been disclosed publicly and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.

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

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


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

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

## Is CVE-2026-18647 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18647 is a medium-severity server-side request forgery vulnerability in jina-ai reader, published on 3 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-18647 exists.

Affected product: jina-ai reader. 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-18647/ (Markdown: https://insights.sbomify.com/CVE-2026-18647/index.md)
```

## Sources

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

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