Menu

Pydantic AI's DNS-Rebind Bypass of Its Egress Allowlist
📰

Pydantic AI's DNS-Rebind Bypass of Its Egress Allowlist

DEV Community: kubernetes·Mike Moore·10 days ago
#5rDXGSpC
#devtokubernetes#devto#dev#hostname#egress
Reading 0:00
15s threshold

Originally published at webofmike.com on 2026-11-06. The demo repo and every command in it were run before publishing.

A DNS record that changes between the moment code checks it and the moment code uses it can beat an egress allowlist that resolves a hostname twice. Pydantic AI patched exactly that bug on 2026-11-04, across v2.66.0, v1.107.10, and pydantic-ai-harness 0.66.0, inside a batch of 10 security advisories disclosed at once . Two of the ten are the same bug class I keep writing about on this site: an egress decision that lives in application code instead of the network.

GHSA-5ppx-9jq6-6pmw (low): allowed_domains on the local web-fetch tool, and PlaywrightBrowser 's egress allowlists, resolved a hostname to check it against the allowlist, then connected to the hostname, which resolved it again. Two lookups, and nothing forced them to agree.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.