How severe is CVE-2022-36937?

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

Is CVE-2022-36937 being actively exploited?

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

What products are affected by CVE-2022-36937?

CVE-2022-36937 primarily affects Facebook Hhvm. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2022-36937?

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

When was CVE-2022-36937 published?

CVE-2022-36937 was published on 2023-05-10 and last updated on 2026-06-17.

CVE-2022-36937

CVE-2022-36937 is a critical-severity vulnerability in Facebook Hhvm with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-327.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
EPSS exploit prediction: 1% (41st percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-327
Affected product: Facebook Hhvm
Published: 2023-05-10
Last modified: 2026-06-17

Description

HHVM 4.172.0 and all prior versions use TLS 1.0 for secure connections when handling tls:// URLs in the stream extension. TLS1.0 has numerous published vulnerabilities and is deprecated. HHVM 4.153.4, 4.168.2, 4.169.2, 4.170.2, 4.171.1, 4.172.1, 4.173.0 replaces TLS1.0 with TLS1.3. Applications that call stream_socket_server or stream_socket_client functions with a URL starting with tls:// are affected.

Frequently asked questions

What is CVE-2022-36937?: HHVM 4.172.0 and all prior versions use TLS 1.0 for secure connections when handling tls:// URLs in the stream extension. TLS1.0 has numerous published vulnerabilities and is deprecated. HHVM 4.153.4, 4.168.2, 4.169.2, 4.170.2, 4.171.1, 4.172.1, 4.173.0 replaces TLS1.0 with TLS1.3. Applications that call stream_socket_server or stream_socket_client functions with a URL starting with tls:// are affected.
How severe is CVE-2022-36937?: CVE-2022-36937 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2022-36937 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (41st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2022-36937?: CVE-2022-36937 primarily affects Facebook Hhvm. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2022-36937?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2022-36937 published?: CVE-2022-36937 was published on 2023-05-10 and last updated on 2026-06-17.

References

Affected products (3)

cpe:2.3:a:facebook:hhvm:*:*:*:*:*:*:*:*
cpe:2.3:a:facebook:hhvm:4.171.0:*:*:*:*:*:*:*
cpe:2.3:a:facebook:hhvm:4.172.0:*:*:*:*:*:*:*

More vulnerabilities in Facebook Hhvm

CVE-2021-24036 — Critical (CVSS 9.8): Passing an attacker controlled size when creating an IOBuf could cause integer overflow, leading to an out of bounds…
CVE-2020-1900 — Critical (CVSS 9.8): When unserializing an object with dynamic properties HHVM needs to pre-reserve the full size of the dynamic property…
CVE-2021-24025 — Critical (CVSS 9.8): Due to incorrect string size calculations inside the preg_quote function, a large input string passed to the function…
CVE-2020-1917 — Critical (CVSS 9.8): xbuf_format_converter, used as part of exif_read_data, was appending a terminating null character to the generated…
CVE-2020-1916 — Critical (CVSS 9.8): An incorrect size calculation in ldap_escape may lead to an integer overflow when overly long input is passed in,…
CVE-2016-1000005 — Critical (CVSS 9.8): mcrypt_get_block_size did not enforce that the provided "module" parameter was a string, leading to type confusion if…

All CVEs affecting Facebook Hhvm →

Other CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) vulnerabilities

CVE-2026-50086 — Critical (CVSS 10.0): The Aqara IAM/SSO gateway (gw-builder.aqara.com) exposes bidirectional AES round-trups against the platform's signing…
CVE-2026-21718 — Critical (CVSS 10.0): An authentication bypass vulnerability exists in Copeland XWEB Pro version 1.12.1 and prior, enabling any attackers to…
CVE-2025-54426 — Critical (CVSS 9.9): Polkadot Frontier is an Ethereum and EVM compatibility layer for Polkadot and Substrate. In versions prior to commit…
CVE-2024-51478 — Critical (CVSS 9.9): YesWiki is a wiki system written in PHP. Prior to 4.4.5, the use of a weak cryptographic algorithm and a hard-coded…
CVE-2026-28252 — Critical (CVSS 9.8): A Use of a Broken or Risky Cryptographic Algorithm vulnerability in Trane Tracer SC, Tracer SC+, and Tracer Concierge…
CVE-2025-13476 — Critical (CVSS 9.8): Rakuten Viber Cloak mode in Android v25.7.2.0g and Windows v25.6.0.0–v25.8.1.0 uses a static and predictable TLS…

Browse all CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) vulnerabilities →