---
id: "CVE-2026-119122"
kind: "vulnerability"
aliases: ["CVE-2026-119122"]
title: "Crawl4AI: Docker server lets API clients reach internal and metadata addresses"
severity: "medium"
cvss: 6.9
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["crawl4ai", "docker", "package", "python", "self-hosted"]
not_affected_if: ["no-untrusted-api-clients", "not-running-docker-server"]
published_at: "2026-10-29T16:18:04+00:00"
first_seen_at: "2026-10-29T16:25:58+00:00"
updated_at: "2026-10-29T16:30:12+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-119122", "first_seen_at": "2026-10-29T16:25:58+00:00"}]
---

# Crawl4AI: Docker server lets API clients reach internal and metadata addresses

Crawl4AI before 0.9.5 has a blind server-side request forgery flaw in its Docker server. An API client can enable check_cache_freshness to bypass the egress proxy and make the server request internal or cloud-metadata addresses, which can reveal internal services.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed Crawl4AI version, for example with `pip show crawl4ai`, and compare it to `0.9.5`.
- Look for whether the Docker server is reachable by untrusted API clients and whether `check_cache_freshness` is accepted in requests.

## Fix

- Crawl4AI: move to `0.9.5` or later.

## Timeline

- 2026-10-29T16:25:58+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-119122

## From the sources

Crawl4AI before 0.9.5 contains a blind server-side request forgery vulnerability in the Docker server that allows API clients to bypass the egress proxy by enabling check_cache_freshness. Attackers can cache a controlled URL, then trigger CacheValidator to follow 302 redirects or DNS rebinding to internal and cloud-metadata addresses for port and service discovery.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_