CVE-2016-8786
No exploitation reported by the sources we read.
- Published2018-03-09
- WeaknessCWE-20
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
Huawei S12700 V200R005C00, V200R006C00, V200R007C00, V200R008C00, S5700 V200R006C00, V200R007C00, V200R008C00, S6700 V200R008C00, S7700 V200R001C00, V200R002C00, V200R003C00, V200R005C00, V200R006C00, V200R007C00, V200R008C00, S9700 V200R001C00, V200R002C00, V200R003C00, V200R005C00, V200R006C00, V200R007C00, V200R008C00 have a denial of service (DoS) vulnerability. Due to the lack of input validation, a remote attacker may craft a malformed Resource Reservation Protocol (RSVP) packet and send it to the device, causing a few buffer overflows and occasional device restart.
Timeline
dates in UTC- 2018-03-0921:29CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2016-8786?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2016-8786?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 200.x | = v200r001c00 | no fix published | NVD |
| 200.x | = v200r002c00 | no fix published | NVD |
| 200.x | = v200r003c00 | no fix published | NVD |
| 200.x | = v200r005c00 | no fix published | NVD |
| 200.x | = v200r006c00 | no fix published | NVD |
| 200.x | = v200r007c00 | no fix published | NVD |
| 200.x | = v200r008c00 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 200.x | = v200r001c00 | no fix published | NVD |
| 200.x | = v200r002c00 | no fix published | NVD |
| 200.x | = v200r003c00 | no fix published | NVD |
| 200.x | = v200r005c00 | no fix published | NVD |
| 200.x | = v200r006c00 | no fix published | NVD |
| 200.x | = v200r007c00 | no fix published | NVD |
| 200.x | = v200r008c00 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 200.x | = v200r005c00 | no fix published | NVD |
| 200.x | = v200r006c00 | no fix published | NVD |
| 200.x | = v200r007c00 | no fix published | NVD |
| 200.x | = v200r008c00 | no fix published | NVD |
2 more products in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
Advisories and patches
- www.huawei.comVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.07.5read 2026-10-23
- NVDCVSS 2.07.8read 2026-10-23
- NVDweakness (CWE)CWE-20read 2026-10-23
- FIRST EPSSEPSS score1.7 %2026-10-22
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Published
- 2018-03-09
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2016-8786?
Is CVE-2016-8786 actively exploited?
What is the CVSS score for CVE-2016-8786?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.