Skip to content
AI/ML

CVE-2026-82638

8.7
High
EPSS 0.30%Sep 1, 2026

SSRF in jina-ai reader allows access to cloud metadata and internal services.

common questions

Is CVE-2026-82638 being exploited?

Not confirmed. CVE-2026-82638 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.30% probability of exploitation in the next 30 days.

How severe is CVE-2026-82638?

CVE-2026-82638 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-82638?

Not known from our data. No patch reference has been recorded for CVE-2026-82638, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-82638 affect?

CVE-2026-82638 affects jina-ai/reader (GitHub), Deployments outside Google Cloud, Containerized ML inference services. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-82638?

Enable private-address guard, block metadata endpoints, restrict outbound HTTP/DNS, apply vendor patch when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
jina-ai/reader (GitHub)Deployments outside Google CloudContainerized ML inference services
impact

Unauthenticated SSRF can retrieve cloud metadata and internal service content, enabling token/credential exfiltration and lateral access.

action required

Immediate action required

affected versions
jina-ai reader
  • affected>= 45d1682db02f0c50b680ad350855da4e38ab2122 and <= 1574bfd380d249c86c82db4dace0d9c8fe17e2b1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free