Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-85699 – Server-Side Request Forgery (SSRF) via Unvalidated Redirects – jina-ai Reader (up t

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-85699 is a Server-Side Request Forgery (SSRF) vulnerability in jina-ai’s Reader project, a service that fetches user-supplied URLs server-side and converts them into LLM-friendly content. The flaw allows an unauthenticated, remote attacker to reach internal network resources and cloud metadata endpoints by abusing HTTP redirects, and carries a High severity rating.

Technical details

  • Root cause: Reader validates the initial request URL against non-public IP ranges (via its assertNormalizedUrl check) but does not re-apply that validation to subsequent redirect hops.
  • Trigger condition: An attacker submits a publicly reachable URL that issues an HTTP redirect to an internal address or a cloud metadata endpoint; the redirect target is fetched without revalidation.
  • Affected code paths: the curl-based fetch path (src/services/curl.ts, src/api/crawler.ts) manually follows redirects without re-checking them, and the browser-based path (src/services/puppeteer.ts) only blocks localhost/127.* in its request interceptor rather than the full non-public IP range.
  • Attack vector: Network, no authentication or user interaction required, low attack complexity.
  • Impact: High confidentiality impact — the server fetches and returns internal/metadata response content to the attacker, enabling disclosure of internal services, credentials, or cloud instance metadata.

Affected software

  • jina-ai Reader — all versions/deployments up to and including commit 1574bfd380d249c86c82db4dace0d9c8fe17e2b1 on the main branch.

Severity

CVSS v4.0 Base Score: 8.7 (High)
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: No tagged patch release has been confirmed at this time; monitor the jina-ai/reader repository for a merged fix (a fix branch addressing hostname/private-IP SSRF has been observed in progress) and upgrade as soon as an official release is available.
  • Workarounds: Disable automatic redirect following in self-hosted Reader deployments, or re-validate the destination of every redirect hop against non-public IP ranges before the request is dispatched; block outbound access from the Reader host to cloud metadata endpoints and internal address ranges at the network/firewall layer; restrict Reader’s egress to an allow-list of external destinations where feasible.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Favicon fingerprint: exact match 1875053947
  • Raw response body: https://r.jina.ai/YOUR_URL, https://s.jina.ai/YOUR_SEARCH_QUERY

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge