CVE-2026-82638
Received Received - Intake

Jina Reader Private-Address Guard Bypass via SSRF

Vulnerability report for CVE-2026-82638, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-30

Last updated on: 2026-08-30

Assigner: VulnCheck

Description

jina-ai reader disables its private-address guard outside Google Cloud deployments, allowing unauthenticated attackers to perform server-side request forgery. Attackers can supply publicly resolvable hostnames mapping to private addresses to retrieve cloud metadata and internal service content.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-30
Last Modified
2026-08-30
Generated
2026-08-30
AI Q&A
2026-08-30
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
jina-ai reader *
jina-ai reader to 1574bfd380d249c86c82db4dace0d9c8fe17e2b1 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-82638 is a Server-Side Request Forgery (SSRF) vulnerability in the jina-ai reader software. It occurs because the private-address guard is disabled outside Google Cloud deployments, allowing unauthenticated attackers to supply hostnames that resolve to private addresses and perform SSRF attacks. This lets attackers retrieve cloud metadata and access internal services.

Detection Guidance

To detect this vulnerability, check if your jina-ai reader instance is running in a self-hosted Docker deployment with default settings. Verify if the service allows requests to private/internal IP addresses via hostnames. Test by attempting to access internal services or cloud metadata endpoints using publicly resolvable hostnames that map to private addresses.

Impact Analysis

An attacker could exploit this to access internal services, including cloud metadata endpoints like AWS IMDS, potentially exposing sensitive data such as IAM credentials. The attack works on self-hosted instances with default Docker settings and requires no authentication.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating GDPR's data protection principles and HIPAA's security requirements for protected health information. Unauthorized data exposure may result in compliance breaches and legal penalties.

Mitigation Strategies

Immediately update jina-ai reader to a patched version beyond commit hash 1574bfd380d249c86c82db4dace0d9c8fe17e2b1. Ensure the environment variable NODE_ENV is set to 'prod' and GCLOUD_PROJECT is configured to enforce private-address guard. Block wildcard DNS services like nip.io in firewall rules.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-82638. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart