CVE-2026-71216

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory published 2026-09-04. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.3
EG Score
5.3(high)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

September 4, 2026

Last Modified

September 8, 2026

Advisory Details (1)

Auto-updated Sep 8, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-71216(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 17× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 19:36 UTCEG score recompute
  2. 2026-09-19 19:36 UTCGHSA enrichment
  3. 2026-09-18 21:23 UTCEG score recompute
  4. 2026-09-18 21:23 UTCGHSA enrichment
  5. 2026-09-18 19:28 UTCEPSS rescore
  6. 2026-09-17 22:17 UTCEG score recompute
  7. 2026-09-17 22:17 UTCGHSA enrichment
  8. 2026-09-17 00:04 UTCEG score recompute
  9. 2026-09-17 00:04 UTCGHSA enrichment
  10. 2026-09-16 14:08 UTCEPSS rescore
  11. 2026-09-16 05:15 UTCEPSS rescore
  12. 2026-09-16 01:51 UTCGHSA enrichment
  13. 2026-09-15 03:38 UTCEG score recompute
  14. 2026-09-15 03:38 UTCGHSA enrichment
  15. 2026-09-15 03:12 UTCEPSS rescore
  16. 2026-09-14 05:25 UTCEG score recompute
  17. 2026-09-14 05:25 UTCGHSA enrichment
  18. 2026-09-13 07:13 UTCGHSA enrichment
  19. 2026-09-12 09:01 UTCEG score recompute
  20. 2026-09-12 09:01 UTCGHSA enrichment
  21. 2026-09-11 14:53 UTCEPSS rescore
  22. 2026-09-11 10:48 UTCEG score recompute
  23. 2026-09-11 10:48 UTCGHSA enrichment
  24. 2026-09-10 12:35 UTCEG score recompute
  25. 2026-09-10 12:35 UTCGHSA enrichment
Show 16 more
  1. 2026-09-10 09:35 UTCEPSS rescore
  2. 2026-09-09 14:22 UTCEG score recompute
  3. 2026-09-09 14:22 UTCGHSA enrichment
  4. 2026-09-08 22:01 UTCEPSS rescore
  5. 2026-09-08 16:09 UTCEG score recompute
  6. 2026-09-08 16:09 UTCGHSA enrichment
  7. 2026-09-08 14:45 UTCEG score recompute 5.30
  8. 2026-09-08 14:45 UTCGHSA enrichment
  9. 2026-09-08 14:44 UTCMITRE cvelistV5CVSS v3 → 5.3 · severity → MEDIUM
  10. 2026-09-08 14:19 UTCGHSA enrichment
  11. 2026-09-07 04:11 UTCEG score recompute
  12. 2026-09-07 04:11 UTCGHSA enrichment
  13. 2026-09-06 13:48 UTCEPSS rescore
  14. 2026-09-04 07:28 UTCNVD update
  15. 2026-09-04 07:04 UTCEG score recompute
  16. 2026-09-04 07:03 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-71216?
CVE-2026-71216 is a medium vulnerability published on September 4, 2026. 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…
When was CVE-2026-71216 disclosed?
CVE-2026-71216 was first published in the National Vulnerability Database on September 4, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-71216 actively exploited?
CVE-2026-71216 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.5% of all scored CVEs.
What is the CVSS score of CVE-2026-71216?
CVE-2026-71216 has a CVSS v3.1 base score of 5.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-71216?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-71216, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-71216

Explore →

Is Your Infrastructure Affected by CVE-2026-71216?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.