CVE-2026-71216: Apache SkyWalking: PagerDuty alarm hook transmits the integration routing key over cleartext HTTP
PagerDuty alarm hook transmits the integration routing key over cleartext HTTP.
PagerDuty serves this endpoint over HTTPS and will normally answer plain HTTP with a redirect. That does not remove the exposure. The initial POST -- including the JSON body containing the routing key -- is written to the socket unencrypted before any redirect response is received. Redirection affects only whether the request is retried securely, not whether the first copy left the host in the clear.
This issue affects Apache SkyWalking: from 9.6.0 through 11.0.0.
Users are recommended to upgrade to version 11.0.0, which fixes the issue.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Apache SkyWalkingto a version that resolves this vulnerability.Fixed in 11.0.0
Event History
Frequently Asked Questions
Which deployments are exposed to routing-key disclosure?
Deployments using the PagerDuty alarm hook with a cleartext HTTP endpoint are exposed because the initial POST body, including the integration routing key, is sent before any HTTPS redirect is received.
What access would be needed to obtain the routing key?
The routing key is transmitted unencrypted in the initial HTTP request. A party able to observe that network traffic could obtain the key from the POST body.
How can I determine whether my SkyWalking deployment is affected?
Review the SkyWalking version and the PagerDuty alarm-hook endpoint configuration. The advisory identifies versions from 9.6.0 through 11.0.0 and recommends upgrading to 11.0.0, while also describing that version as the fix.