How severe is CVE-2020-13991?

CVE-2020-13991 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.

Is CVE-2020-13991 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (82nd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2020-13991?

CVE-2020-13991 affects Jerryscript. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2020-13991?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2020-13991 published?

CVE-2020-13991 was published on 2020-09-24 and last updated on 2026-06-17.

CVE-2020-13991

CVE-2020-13991 is a high-severity vulnerability in Jerryscript with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v2: 5.0
EPSS exploit prediction: 2% (82nd percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Jerryscript
Published: 2020-09-24
Last modified: 2026-06-17

Description

vm/opcodes.c in JerryScript 2.2.0 allows attackers to hijack the flow of control by controlling a register.

Frequently asked questions

What is CVE-2020-13991?: vm/opcodes.c in JerryScript 2.2.0 allows attackers to hijack the flow of control by controlling a register.
How severe is CVE-2020-13991?: CVE-2020-13991 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2020-13991 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (82nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-13991?: CVE-2020-13991 affects Jerryscript. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2020-13991?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2020-13991 published?: CVE-2020-13991 was published on 2020-09-24 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:jerryscript:jerryscript:2.2.0:*:*:*:*:*:*:*

More vulnerabilities in Jerryscript

CVE-2023-36109 — Critical (CVSS 9.8): Buffer Overflow vulnerability in JerryScript version 3.0, allows remote attackers to execute arbitrary code via…
CVE-2023-38961 — Critical (CVSS 9.8): Buffer Overflwo vulnerability in JerryScript Project jerryscript v.3.0.0 allows a remote attacker to execute arbitrary…
CVE-2020-22597 — Critical (CVSS 9.8): An issue in Jerrscript- project Jerryscrip v. 2.3.0 allows a remote attacker to execute arbitrary code via the…
CVE-2021-42863 — Critical (CVSS 9.8): A buffer overflow in ecma_builtin_typedarray_prototype_filter() in JerryScript version fe3a5c0 allows an attacker to…
CVE-2021-43453 — Critical (CVSS 9.8): A Heap-based Buffer Overflow vulnerability exists in JerryScript 2.4.0 and prior versions via an out-of-bounds read in…
CVE-2021-41752 — Critical (CVSS 9.8): Stack overflow vulnerability in Jerryscript before commit e1ce7dd7271288be8c0c8136eea9107df73a8ce2 on Oct 20, 2021 due…

All CVEs affecting Jerryscript →