Plan
active
GitHub webhook IP ranges added to Meta API hooks field
- Platform/SRE — Plan: If your org maintains a firewall or security-group allowlist for incoming GitHub webhook traffic, update it to include the new IP ranges from the Meta API hooks field before deployments that rely on webhooks start failing.
- CI/CD — Plan: Pipelines that trigger via GitHub webhooks and sit behind a strict inbound allowlist may silently drop deliveries; pull the updated ranges from the Meta API and refresh your allowlist rules.
- Leader — Skip
This entry was curated and judged by AI (Claude) with automated enrichment
(CISA KEV / EPSS / public PoC). Verify against the original source before
acting. Found a bad verdict?
Report it —
confirmed errors go to the corrections log.