CDN Cache Poisoning Incident Alters Script Delivery
Cache key confusion in a CDN edge path enabled temporary script poisoning for some routes. Affected pages loaded credential-harvesting JavaScript before purge.
## What happened An edge caching rule mismatch allowed attacker-controlled responses to be served across tenants. ## Why this matters beyond one victim CDNs are central distribution layers. Misconfiguration can fan out malicious content at internet scale. ## Technical notes Strict origin response headers and signed asset pipelines helped detect and contain impact faster.
CONTENT OPTIMIZATION · AEO/GEO
Not yet scored. Next refresh: 02:00 UTC.
audit trail / provenance0
Provenance
Claims tie surfaced fields back to sources, models, or heuristics.
No structured claims yet — severity uplift rationale still applies below.
What changed
Append-only revisions when ingest or analysts evolve the record.
No revision rows stored yet.
discussion
Sign in to join the thread and vote on comments.
Loading comments…