CVE-2020-1918

What it is

In-memory file operations (ie: using fopen on a data URI) did not properly restrict negative seeking, allowing for the reading of memory prior to the in-memory buffer. This issue affects HHVM versions prior to 4.56.3, all versions between 4.57.0 and 4.80.1, all versions between 4.81.0 and 4.93.1, and versions 4.94.0, 4.95.0, 4.96.0, 4.97.0, 4.98.0.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data exposure.

Exploit odds

1.2% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2021-03-10 16:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 03:02 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.2% in the next 30 days (EPSS).
• Severity: 7.5 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2021-03-10 16:15 UTC

Last modified

2026-06-17 03:02 UTC

Exploit probability

1.2% · EPSS, next 30 days

Weakness

CWE-127

Record status

Modified

Affected

• Facebook Hhvm < 4.56.3
• Facebook Hhvm < 4.80.2
• Facebook Hhvm < 4.93.2
• Facebook Hhvm 4.94.0
• Facebook Hhvm 4.95.0
• Facebook Hhvm 4.96.0
• Facebook Hhvm 4.97.0
• Facebook Hhvm 4.98.0

Attack profile CVSS 3.1 · 7.5

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2020-1918.md and follow it. Check whether this project is affected by CVE-2020-1918. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge