Skip to main content

jina-ai Reader CVE-2026-18647

| EUVDEUVD-2026-52435 MEDIUM
Server-Side Request Forgery (SSRF) (CWE-918)
2026-08-03 VulDB GHSA-4xp8-858j-g46w
5.5
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Submit crafted internal URL to public Reader API
  2. Exploit
    isValidTLD fails to reject non-public target
  3. Execution
    Puppeteer fetches internal resource on server's behalf
  4. Impact
    Internal response data returned to attacker

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Credential Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

The jina-ai Reader service must be network-accessible by the attacker. No authentication is required (CVSS 4.0 PR:N). The triggering condition is any user-supplied URL or domain input routed through the isValidTLD function in the Crawler/Puppeteer cloud function - this is the service's core crawl functionality, not an edge-case configuration. The practical impact is bounded by the network reachability of the Puppeteer process: if the host has no access to internal networks or cloud metadata endpoints, confidentiality and integrity impact is reduced to external resource abuse. All known deployments up to commit 1574bfd are affected with no safe downgrade target due to the rolling release model. Exploitation is not limited by user interaction, authentication, or non-default configuration - the crawler's intended public API surface is the attack vector.

Impact

The CVSS 4.0 base score of 5.5 (Medium) with vector AV:N/AC:L/AT:N/PR:N/UI:N reflects unauthenticated, low-complexity remote exploitation. The supplemental E:P metric confirms a PoC exists, elevating realistic exploitability above a theoretical rating. All three impact metrics are rated Low (VC:L/VI:L/VA:L), which typically understates SSRF risk: even partial internal resource access can expose cloud IAM credentials via metadata services or enable internal service enumeration, making real-world impact highly environment-dependent. The product is not listed in CISA KEV, and no EPSS data was provided, so widespread automated exploitation is unconfirmed but cannot be excluded given the public PoC. The vendor's non-response to disclosure means no official remediation exists, compounding risk for all current deployments. This is a genuine priority for any deployment of jina-ai Reader with internal network access or cloud-hosted infrastructure.

Exploit ScenarioDerived

An unauthenticated attacker submits a crafted URL targeting an internal address - such as http://169.254.169.254/latest/meta-data/iam/security-credentials/ - to the jina-ai Reader crawling endpoint. The isValidTLD validation function fails to reject the non-public domain, and the Puppeteer headless browser fetches the cloud metadata endpoint on the attacker's behalf, returning IAM credentials or internal service responses. A public proof-of-concept demonstrating this technique is available at https://github.com/orionyan520/cve_report/issues/8, substantially lowering the skill bar for exploitation.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 03, 2026

Server-side request forgery in jina-ai Reader's Puppeteer-based crawler allows unauthenticated remote attackers to manipulate the isValidTLD function to coerce the server into issuing arbitrary HTTP requests to internal or restricted network targets. All deployments up to commit 1574bfd380d249c86c82db4dace0d9c8fe17e2b1 are affected with no vendor-issued patch, as the maintainers did not respond to disclosure. A public proof-of-concept exploit exists (no CISA KEV listing), and the rolling release model means there is no safe pinned version for operators to target.

RemediationAI

No vendor-released patch has been identified at time of analysis - the vendor did not respond to responsible disclosure. Operators should inspect the git history of /backend/functions/src/cloud-functions/crawler.ts for commits newer than 1574bfd380d249c86c82db4dace0d9c8fe17e2b1 that harden the isValidTLD function before upgrading, as no officially confirmed fix commit is available. As immediate compensating controls: restrict network egress from the Puppeteer/crawler process to an explicit allowlist of external domains, blocking RFC 1918 ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), link-local addresses (169.254.0.0/16, which hosts cloud metadata services), and loopback. If cloud-hosted on AWS, enforce IMDSv2 to neutralize metadata-based credential theft via SSRF - note this does not eliminate the SSRF itself but limits its blast radius. Placing the crawler behind a forward HTTP proxy that enforces domain allowlisting is a stronger control, though it may restrict intended crawl functionality. Monitor VulDB at https://vuldb.com/vuln/385566 for vendor patch confirmation.

Affected VersionsENISA

Reader 1574bfd380d249c86c82db4dace0d9c8fe17e2b1

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

jina-ai Reader (CPE: cpe:2.3:a:jina-ai:reader:*:*:*:*:*:*:*:*) is an AI-powered web content ingestion service that uses Puppeteer - a headless Chromium automation library - to fetch and process remote URLs as cloud functions. The vulnerable component is the isValidTLD function within /backend/functions/src/cloud-functions/crawler.ts. The root cause is CWE-918 (Server-Side Request Forgery): user-controlled URL or domain inputs are insufficiently validated before being passed to Puppeteer for fetching, allowing attackers to supply URLs that resolve to internal RFC 1918 addresses, cloud metadata endpoints (e.g., AWS IMDSv1 at 169.254.169.254), or other restricted services. Puppeteer's full browser stack can follow redirects and handle complex schemes, expanding the SSRF attack surface beyond simple HTTP libraries.

Know when Reader gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulDB) PRIMARY 5.5 MEDIUM
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
vuln.today AI 6.5 MEDIUM

Network-accessible unauthenticated SSRF with no scope change; low confidentiality and integrity from internal resource access; no availability impact supported by the description.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
Low
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
CVSS changed
Aug 03, 2026 - 21:22 NVD
6.9 (MEDIUM) 5.5 (MEDIUM)
CVE Published
Aug 03, 2026 - 20:45 cve.org
MEDIUM 5.5

DescriptionCVE.org

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.

Threat Intelligence Overview

EPSS Score
0.4%
Top 72% exploitable
Prevalence
Low
niche AI web reader tool, limited enterprise production footprint
Exploit
POC
Public exploit code exists
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.4%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

48
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +28
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.

More in Reader

View all
CVE-2016-4203 CRITICAL POC
9.8 Jul 13

Adobe Reader and Acrobat before 11.0.17, Acrobat and Acrobat Reader DC Classic before 15.006.30198, and Acrobat and Acro

CVE-2016-4208 CRITICAL POC
9.8 Jul 13

Adobe Reader and Acrobat before 11.0.17, Acrobat and Acrobat Reader DC Classic before 15.006.30198, and Acrobat and Acro

CVE-2016-4207 CRITICAL POC
9.8 Jul 13

Adobe Reader and Acrobat before 11.0.17, Acrobat and Acrobat Reader DC Classic before 15.006.30198, and Acrobat and Acro

CVE-2016-4206 CRITICAL POC
9.8 Jul 13

Adobe Reader and Acrobat before 11.0.17, Acrobat and Acrobat Reader DC Classic before 15.006.30198, and Acrobat and Acro

CVE-2016-4205 CRITICAL POC
9.8 Jul 13

Adobe Reader and Acrobat before 11.0.17, Acrobat and Acrobat Reader DC Classic before 15.006.30198, and Acrobat and Acro

CVE-2016-4204 CRITICAL POC
9.8 Jul 13

Adobe Reader and Acrobat before 11.0.17, Acrobat and Acrobat Reader DC Classic before 15.006.30198, and Acrobat and Acro

CVE-2016-4201 CRITICAL POC
9.8 Jul 13

Adobe Reader and Acrobat before 11.0.17, Acrobat and Acrobat Reader DC Classic before 15.006.30198, and Acrobat and Acro

CVE-2016-1077 CRITICAL POC
9.8 May 11

Adobe Reader and Acrobat before 11.0.16, Acrobat and Acrobat Reader DC Classic before 15.006.30172, and Acrobat and Acro

CVE-2017-11211 HIGH
8.8 Aug 11

Adobe Acrobat Reader 2017.009.20058 and earlier, 2017.008.30051 and earlier, 2015.006.30306 and earlier, and 11.0.20 and

CVE-2017-3117 HIGH
8.8 Aug 11

Adobe Acrobat Reader 2017.009.20058 and earlier, 2017.008.30051 and earlier, 2015.006.30306 and earlier, and 11.0.20 and

CVE-2019-5031 HIGH POC
8.8 Oct 02

An exploitable memory corruption vulnerability exists in the JavaScript engine of Foxit Software's Foxit PDF Reader, ver

CVE-2018-3997 HIGH POC
8.8 Oct 08

An exploitable use-after-free vulnerability exists in the JavaScript engine of Foxit Software's Foxit PDF Reader, versio

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy