The vulnerability exposes the PagerDuty integration routing key in the initial POST request sent over cleartext HTTP. The JSON body containing the routing key is transmitted unencrypted before any redirect, so the key can be captured by anyone able to intercept the traffic. This allows an attacker to obtain a credential that can authenticate to PagerDuty and potentially submit alerts or manipulate routing rules, compromising the confidentiality of the integration configuration. The weakness is classified as CWE-319, plaintext transmission of sensitive information.

Apache SkyWalking versions from 9.6.0 through 11.0.0 are affected. The software is distributed by the Apache Software Foundation as part of the SkyWalking observability platform, and any deployment using these versions and configured to use PagerDuty alarm hooks is vulnerable.

The EPSS score is not available and the vulnerability is not listed in the CISA KEV catalog, indicating no known active exploitation. However, the exposure of an authentication credential can enable wide-ranging impacts if intercepted. While no vector is explicitly stated, the likely attack path involves network interception of the initial HTTP POST to PagerDuty, so systems that allow unauthenticated network traffic to the external PagerDuty endpoint are at risk. Given the sensitivity of the exposed key, the risk is considered high even without an active exploit.