Unverified50% confidenceFactExact time
mcp-server-fetch now rejects NAT64 requests in the 64:ff9b::/96 range that encapsulate private, loopback, or link-local IPv4 addresses (GHSA-66qx-2266-pmj6).
1
Sources
50%
Confidence
Long-term
Relevance
10/25/2026
First Seen
Sources
Related Entities
Related Claims
Unverified127.0.0.1 is the loopback address in IPv4, and a service bound to that address only accepts connections from the same machine and cannot be accessed from the LAN or the public internet; listening on 0.0.0.0, by contrast, accepts connections from all network interfaces.71% similarUnverifiedThe IPv6 address 2001:db8::1 is expanded to 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa in ip6.arpa reverse resolution.64% similarUnverifiedThere are two officially recommended ways to mitigate the Docker bypassing ufw problem: one is to bind container ports to 127.0.0.1 and expose services uniformly through an Nginx/Caddy reverse proxy; the other is to set iptables: false in /etc/docker/daemon.json, but this affects all container networking functionality and is generally not recommended.57% similarUnverifiedAfter starting, N8N serves by default at localhost:5678.57% similarUnverifiedv0.5 adds operation options such as Block IP address and Leave the process alone to the connection table.57% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1094935API
curl https://kongchang.com/api/v1/knowledge/claims/1094935MCP
get_claim(id=1094935)