CVE-2017-8359

CRITICALNVD 9.89.8—

9.8

Google gRPC before 2017-03-29 has an out-of-bounds write caused by a heap-based use-after-free related to the grpc_call_destroy function in core/lib/surface/call.c.

CVSS v3: 9.8
EG Score: 9.8(medium)
EPSS: 83.2%
KEV: Not listed

Published

April 30, 2017

Last Modified

May 13, 2026

Advisory Details (3)

Auto-updated May 15, 2026

No patch confirmed yet.

generic

Remove call from sibling list when it is not first child. by yang-g · Pull Request #10353 · grpc/grpc · GitHub

https://github.com/grpc/grpc/pull/10353

generic

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=726

generic

http://www.securityfocus.com/bid/98280

Affected Packages

(1 across 1 ecosystem)

PyPI(1)

Package	Vulnerable range	Fixed in	Dependents
grpcio	0.10.0a0 ... 1.2.1 (41 versions)	1.3.0	—

Data Freshness Timeline

(refreshed 11× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-30 20:23 UTCOSV refresh
2026-05-29 13:41 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-22 21:15 UTCepss_batch
2026-05-22 21:15 UTCepss_batch
2026-05-22 21:15 UTCepss_batch
2026-05-22 21:15 UTCepss_batch

Frequently asked(5)

What is CVE-2017-8359?

CVE-2017-8359 is a critical vulnerability published on April 30, 2017. Google gRPC before 2017-03-29 has an out-of-bounds write caused by a heap-based use-after-free related to the grpccalldestroy function in core/lib/surface/call.c.

When was CVE-2017-8359 disclosed?

CVE-2017-8359 was first published in the National Vulnerability Database on April 30, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2017-8359 actively exploited?

CVE-2017-8359 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 83.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2017-8359?

CVE-2017-8359 has a CVSS v3 base score of 9.8 (NVD).

How do I remediate CVE-2017-8359?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-8359, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-8359

Explore →

Is Your Infrastructure Affected by CVE-2017-8359?

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

Start Free Scan →Browse All CVEs

CVE-2017-8359

📅 Published

🔄 Last Modified

📋 Advisory Details (3)

Remove call from sibling list when it is not first child. by yang-g · Pull Request #10353 · grpc/grpc · GitHub

Affected Packages

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2017-8359?

Published

Last Modified

Advisory Details (3)

Frequently asked(5)