CVE-2020-36851
UNSCOREDDescription
Rob--W cors-anywhere instances configured as an open proxy allow unauthenticated external users to induce the server to make HTTP requests to arbitrary targets (SSRF). Because the proxy forwards requests and headers, an attacker can reach internal-only endpoints and link-local metadata services, retrieve instance role credentials or other sensitive metadata, and interact with internal APIs and services that are not intended to be internet-facing. The vulnerability is exploitable by sending crafted requests to the proxy with the target resource encoded in the URL; many cors-anywhere deployments forward arbitrary methods and headers (including PUT), which can permit exploitation of IMDSv2 workflows as well as access to internal management APIs. Successful exploitation can result in theft of cloud credentials, unauthorized access to internal services, remote code execution or privilege escalation (depending on reachable backends), data exfiltration, and full compromise of cloud resources. Mitigation includes: restricting the proxy to trusted origins or authentication, whitelisting allowed target hosts, preventing access to link-local and internal IP ranges, removing support for unsafe HTTP methods/headers, enabling cloud provider mitigations, and deploying network-level protections.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3.1 Vector
No CVSS vector data available.
Exploit Intelligence
Moderate risk: more likely to be exploited than 60% of all known CVEs.
References
Related Vulnerabilities
Other CWE-918 (Server-Side Request Forgery (SSRF)) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2024-21893 | High | 8.2 | 100% | KEV + Ransom | - |
| CVE-2021-40438 | Critical | 9.0 | 100% | KEV + Ransom | Fix |
| CVE-2021-34473 | Critical | 9.1 | 100% | KEV + Ransom | Fix |
| CVE-2021-26855 | Critical | 9.1 | 100% | KEV + Ransom | Fix |
| CVE-2021-21985 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2022-41040 | High | 8.8 | 100% | KEV + Ransom | Fix |
Common questions
How do I fix CVE-2020-36851?
No published fix for CVE-2020-36851 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2020-36851 being actively exploited?
Not that we know of. CVE-2020-36851 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 1.0% is the estimated probability that it will be exploited in the next 30 days. That is higher than 60% of all scored CVEs.
Embed a live status badge for CVE-2020-36851
Markdown
[](https://tridentstack.com/cve/CVE-2020-36851)HTML
<a href="https://tridentstack.com/cve/CVE-2020-36851"><img src="https://tridentstack.com/cve/badge/CVE-2020-36851.svg" alt="CVE-2020-36851"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-05-26.