No exploitation reportedFix available

CVE-2020-1913

Q: Is CVE-2020-1913 actively exploited?

Active exploitation of CVE-2020-1913 has not been confirmed. Its EPSS score was 1.2% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

Q: What is the CVSS score for CVE-2020-1913?

CVE-2020-1913 has a CVSS v3 base score of 8.1 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.

No exploitation reported by the sources we read.

Published2020-09-09
WeaknessCWE-195 · CWE-681

Am I 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

An Integer signedness error in the JavaScript Interpreter in Facebook Hermes prior to commit 2c7af7ec481ceffd0d14ce2d7c045e475fd71dc6 allows attackers to cause a denial of service attack or a potential RCE via crafted JavaScript. Note that this is only exploitable if the application using Hermes permits evaluation of untrusted JavaScript. Hence, most React Native applications are not affected.

Timeline

dates in UTC

2020-09-0919:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC

Indicators tagged with this CVE, per day0 indicators over 7 days

Block these indicators

Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2020-1913?format=txt
CSV export: https://api.ismalicious.com/edl/cve/CVE-2020-1913?format=csv
TAXII collection of exploited CVEs
The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD · OSV

Facebook hermes

Branch	Affected	Fixed in	Source
0.4	≤ 0.4.3	no fix published	NVD

hermes-engine

Branch	Affected	Fixed in	Source
0.5	< 0.5.2	0.5.2	OSV

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

Advisories and patches

github.comPatch
www.facebook.comVendor Advisory

Detection

Nuclei template: none so far
Exploit-DB: no entry
Proof-of-concept repositories: none listed

Sources

NVDCVSS 3.18.1read 2026-10-23
NVDCVSS 2.06.8read 2026-10-23
CNAweakness (CWE)CWE-195read 2026-10-23
NVDweakness (CWE)CWE-681read 2026-10-23
FIRST EPSSEPSS score1.2 %2026-10-23
OSVaffected packages—

Technical details

CVSS v3 Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Published: 2020-09-09
Last Modified: 2026-06-17
NVD status: Modified

Frequently asked questions

What is CVE-2020-1913?

Is CVE-2020-1913 actively exploited?

Active exploitation of CVE-2020-1913 has not been confirmed. Its EPSS score was 1.2% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2020-1913?

CVE-2020-1913 has a CVSS v3 base score of 8.1 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.

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 ».

Get alerts for this product CISA KEV additions, October 2026 Search CVEs

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.

Back to CVE Database