Quick answers
- Is CVE-2026-85699 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-85699 being exploited in the wild.
- How severe is CVE-2026-85699?
- High severity, with a CVSS score of 7.5, published 4 September 2026.
- Which products and versions are affected?
- jina-ai reader prior to fix.
- Is there a fix for CVE-2026-85699?
- 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-85699 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-85699?
- Check whether anything you run is named in the advisory. 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 is a server-side request forgery (SSRF) resulting from incomplete URL validation in the redirect handling logic. The vulnerable component (curl.ts) validates the initial URL against a blocklist but does not re-apply validation to the target of HTTP redirects. An attacker can host a public server that responds with a redirect pointing to internal IP addresses (e.g., 127.0.0.1, 169.254.169.254 AWS metadata) or private cloud endpoints. When the Reader service follows the redirect, it fetches the response from the internal target and returns the body to the attacker. No authentication is required—an attacker only needs to craft the initial URL and wait for the service to fetch it. Patches are available in the GitHub repository.
Affected products
- jina-ai reader prior to fix
Timeline
- 2026-09-04: disclosed
- other: CVE-2026-85699 assigned