CVE-2026-87724

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory published 2026-09-09. a secondary CVSS source baseline 6.5; sources differ by 0.0.

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

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

Tor before 0.4.9.12 interprets the CC_RESPONSE extension even when CC_REQUEST was not sent, which allows remote attackers to cause a denial of service (crash) because of corrupted congestion-control state. This is TROVE-2026-032.

CVSS v3
6.5
EG Score
6.5(high)
EG Risk
29(Track)
EG Risk 29/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
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
18%
KEV
Not listed

Published

September 9, 2026

Last Modified

September 9, 2026

Advisory Details (1)

Auto-updated Sep 9, 2026
No patch confirmed yet.
generic

Reject CC_RESPONSE extension if we did not send CC_REQUEST. (10d4b8ff) · Commits · torproject / tor · GitLab

https://gitlab.com/torproject/tor/-/commit/10d4b8ffefa7c00aab2b631ed7e7f15e42cd012d

Vendor Advisories for CVE-2026-87724(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 / 32× 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-18 19:28 UTCEPSS rescore
  2. 2026-09-18 14:59 UTCEG score recompute
  3. 2026-09-18 14:59 UTCGHSA enrichment
  4. 2026-09-17 19:32 UTCEPSS rescore
  5. 2026-09-17 15:30 UTCGHSA enrichment
  6. 2026-09-16 15:52 UTCEG score recompute
  7. 2026-09-16 15:52 UTCGHSA enrichment
  8. 2026-09-16 14:09 UTCEPSS rescore
  9. 2026-09-16 05:15 UTCEPSS rescore
  10. 2026-09-15 16:23 UTCEG score recompute
  11. 2026-09-15 16:23 UTCGHSA enrichment
  12. 2026-09-15 03:12 UTCEPSS rescore
  13. 2026-09-14 16:54 UTCGHSA enrichment
  14. 2026-09-13 17:25 UTCEG score recompute
  15. 2026-09-13 17:25 UTCGHSA enrichment
  16. 2026-09-12 17:56 UTCEG score recompute
  17. 2026-09-12 17:56 UTCGHSA enrichment
  18. 2026-09-11 18:27 UTCEG score recompute
  19. 2026-09-11 18:27 UTCGHSA enrichment
  20. 2026-09-11 14:53 UTCEPSS rescore
  21. 2026-09-11 14:53 UTCEPSS rescore
  22. 2026-09-10 18:58 UTCEG score recompute
  23. 2026-09-10 18:58 UTCGHSA enrichment
  24. 2026-09-09 19:29 UTCEG score recompute
  25. 2026-09-09 19:29 UTCGHSA enrichment
Show 7 more
  1. 2026-09-09 18:21 UTCEG score recompute
  2. 2026-09-09 18:21 UTCGHSA enrichment
  3. 2026-09-09 16:08 UTCEG score recompute
  4. 2026-09-09 16:08 UTCGHSA enrichment
  5. 2026-09-09 02:37 UTCEG score recompute
  6. 2026-09-09 01:38 UTCEG score recompute
  7. 2026-09-09 01:37 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-87724?
CVE-2026-87724 is a medium vulnerability published on September 9, 2026. Tor before 0.4.9.12 interprets the CCRESPONSE extension even when CCREQUEST was not sent, which allows remote attackers to cause a denial of service (crash) because of corrupted congestion-control state. This is TROVE-2026-032.
When was CVE-2026-87724 disclosed?
CVE-2026-87724 was first published in the National Vulnerability Database on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-87724 actively exploited?
CVE-2026-87724 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 82.0% of all scored CVEs.
What is the CVSS score of CVE-2026-87724?
CVE-2026-87724 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-87724?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-87724, 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-87724

Explore →

Is Your Infrastructure Affected by CVE-2026-87724?

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

Start Free Scan →Browse All CVEs