CVE-2026-72552

The CVSS 7.5 rating on this vulnerability obscures a critical risk: the metatags edge endpoint fetches caller-supplied URLs without any denylist, allowlist, or access control. In any cloud deployment, this directly exposes the metadata service at 169.254.169.254 — AWS, GCP, and Azure all use this address for IAM role credentials, instance tokens, and configuration data. A successful SSRF exploit here escalates from URL fetch to full account compromise in seconds, not because of a complex attack chain, but because the metadata endpoint is architecturally available by default in cloud environments. The 'without applying a denylist' phrasing is the key detail. This isn't a denylist that was bypassed — it's a complete absence of URL validation, meaning any external requester can trigger the endpoint to fetch arbitrary URLs. The edge function context compounds this: edge functions often operate with elevated privileges and may have different network policies than the main application tier, creating paths to internal services that wouldn't exist from a standard API route. Prioritize this remediation above what the CVSS score suggests. Verify whether the edge function runs in a shared or isolated network namespace, and confirm whether egress to metadata addresses was explicitly blocked at the infrastructure level. If your deployment runs on any major cloud provider and the function has outbound HTTP capability, treat the metadata endpoint as accessible until proven otherwise. The gap between a 7.5 rating and the actual blast radius in cloud-native environments is substantial — this is the kind of vulnerability where the scoring system's conservative assumptions about network isolation no longer hold.

Reviewed through automated stages and approved by a human before publication.