An issue was discovered in Erlang/OTP 18.x. Erlang's generation of compiled regular expressions is vulnerable to a heap overflow. Regular expressions using a malformed extpattern can indirectly specify an offset that is used as an array index. This ordinal permits arbitrary regions within the erts_alloc arena to be both read and written to.
This vulnerability carries a CRITICAL severity rating with a CVSS v3.1 score of 9.8, indicating it can be exploited remotely over the network with relatively low complexity without requiring user interaction and does not require pre-existing privileges . The vulnerability impacts confidentiality (data exposure), integrity (unauthorized modifications), and availability (service disruption) for affected systems. Impacting 1 product from erlang organizations running these solutions should prioritize assessment and patching.
First disclosed in 2017, this vulnerability was reported during a period defined by widespread IoT adoption challenges, mobile security concerns, and the emergence of advanced persistent threat (APT) techniques. Contemporary mitigation strategies focused on secure development practices and third-party component vetting.
2017-03-18T20:59:00.127
2026-05-13T00:24:29.033
Modified
CVSSv3.0: 9.8 (CRITICAL)
AV:N/AC:L/Au:N/C:P/I:P/A:P
10.0
6.4
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | erlang | erlang\/otp | 18.0 | Yes |
| Application | erlang | erlang\/otp | 18.0 | Yes |
| Application | erlang | erlang\/otp | 18.0 | Yes |
| Application | erlang | erlang\/otp | 18.0.1 | Yes |
| Application | erlang | erlang\/otp | 18.0.2 | Yes |
| Application | erlang | erlang\/otp | 18.0.3 | Yes |
| Application | erlang | erlang\/otp | 18.1 | Yes |
| Application | erlang | erlang\/otp | 18.1.1 | Yes |
| Application | erlang | erlang\/otp | 18.1.2 | Yes |
| Application | erlang | erlang\/otp | 18.1.3 | Yes |
| Application | erlang | erlang\/otp | 18.1.4 | Yes |
| Application | erlang | erlang\/otp | 18.1.5 | Yes |
| Application | erlang | erlang\/otp | 18.2 | Yes |
| Application | erlang | erlang\/otp | 18.2.1 | Yes |
| Application | erlang | erlang\/otp | 18.2.2 | Yes |
| Application | erlang | erlang\/otp | 18.2.3 | Yes |
| Application | erlang | erlang\/otp | 18.2.4 | Yes |
| Application | erlang | erlang\/otp | 18.2.4.1 | Yes |
| Application | erlang | erlang\/otp | 18.3 | Yes |
| Application | erlang | erlang\/otp | 18.3.1 | Yes |
| Application | erlang | erlang\/otp | 18.3.2 | Yes |
| Application | erlang | erlang\/otp | 18.3.3 | Yes |
| Application | erlang | erlang\/otp | 18.3.4 | Yes |
| Application | erlang | erlang\/otp | 18.3.4.1 | Yes |
| Application | erlang | erlang\/otp | 18.3.4.2 | Yes |
| Application | erlang | erlang\/otp | 18.3.4.3 | Yes |
| Application | erlang | erlang\/otp | 18.3.4.4 | Yes |
| Application | erlang | erlang\/otp | 18.3.4.5 | Yes |
| Application | erlang | erlang\/otp | 19.0 | Yes |
| Application | erlang | erlang\/otp | 19.0 | Yes |
| Application | erlang | erlang\/otp | 19.0 | Yes |
| Application | erlang | erlang\/otp | 19.0.1 | Yes |
| Application | erlang | erlang\/otp | 19.0.2 | Yes |
| Application | erlang | erlang\/otp | 19.0.3 | Yes |
| Application | erlang | erlang\/otp | 19.0.4 | Yes |
| Application | erlang | erlang\/otp | 19.0.5 | Yes |
| Application | erlang | erlang\/otp | 19.0.6 | Yes |
| Application | erlang | erlang\/otp | 19.0.7 | Yes |
| Application | erlang | erlang\/otp | 19.1 | Yes |
| Application | erlang | erlang\/otp | 19.1.1 | Yes |
| Application | erlang | erlang\/otp | 19.1.2 | Yes |
| Application | erlang | erlang\/otp | 19.1.3 | Yes |
| Application | erlang | erlang\/otp | 19.1.4 | Yes |
| Application | erlang | erlang\/otp | 19.1.5 | Yes |
| Application | erlang | erlang\/otp | 19.1.6 | Yes |
| Application | erlang | erlang\/otp | 19.1.6.1 | Yes |
| Application | erlang | erlang\/otp | 19.2 | Yes |
| Application | erlang | erlang\/otp | 19.2.1 | Yes |
| Application | erlang | erlang\/otp | 19.2.2 | Yes |
| Application | erlang | erlang\/otp | 19.2.3 | Yes |
| Application | erlang | erlang\/otp | 19.2.3.1 | Yes |
| Application | erlang | erlang\/otp | 19.3 | Yes |
| Application | erlang | erlang\/otp | 19.3.1 | Yes |
| Application | erlang | erlang\/otp | 19.3.2 | Yes |
| Application | erlang | erlang\/otp | 19.3.3 | Yes |
| Application | erlang | erlang\/otp | 19.3.4 | Yes |
| Application | erlang | erlang\/otp | 19.3.5 | Yes |
| Application | erlang | erlang\/otp | 19.3.6 | Yes |
| Application | erlang | erlang\/otp | 19.3.6.1 | Yes |
| Application | erlang | erlang\/otp | 19.3.6.2 | Yes |
| Application | erlang | erlang\/otp | 19.3.6.3 | Yes |
| Application | erlang | erlang\/otp | 19.3.6.4 | Yes |
| Application | erlang | erlang\/otp | 19.3.6.5 | Yes |
| Application | erlang | erlang\/otp | 19.3.6.6 | Yes |
| Application | erlang | erlang\/otp | 19.3.6.7 | Yes |
| Application | erlang | erlang\/otp | 19.3.6.8 | Yes |
| Application | erlang | erlang\/otp | 19.3.6.9 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For erlang's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.