An issue was discovered in Erlang/OTP 18.x.
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.
- Published
- Mar 18, 2017
- Updated
- Jun 16, 2026
- EPSS
- 1.5% · 73th percentile
- CWE
- CWE-119
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.5%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| erlang | erlang\/otp | cpe:2.3:a:erlang:erlang\/otp |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- erlang erlang/otp18.0
- erlang erlang/otp18.0.1
- erlang erlang/otp18.0.2
- erlang erlang/otp18.0.3
- erlang erlang/otp18.1
- erlang erlang/otp18.1.1
- erlang erlang/otp18.1.2
- erlang erlang/otp18.1.3
- erlang erlang/otp18.1.4
- erlang erlang/otp18.1.5
- erlang erlang/otp18.2
- erlang erlang/otp18.2.1
- erlang erlang/otp18.2.2
- erlang erlang/otp18.2.3
- erlang erlang/otp18.2.4
- erlang erlang/otp18.2.4.1
- erlang erlang/otp18.3
- erlang erlang/otp18.3.1
- erlang erlang/otp18.3.2
- erlang erlang/otp18.3.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | erlang | before 1:19.2.1+dfsg-2 | 1:19.2.1+dfsg-2 |
| SUSE:Package Hub 12 | erlang | before 18.3.4.7-9.1 | 18.3.4.7-9.1 |
Same product
erlang: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-32433Erlang/OTP SSH Vulnerable to Pre-Authentication RCEKEV100Now
- CVE-2022-37026In Erlang/OTP before 23.3.4.15, 24.x before 24.3.4.2, and 25.x before 25.0.2, there is a Client Authentication Bypass in certain client-cert39Monitor
- CVE-2026-55953TLS 1.2 and DTLS client accepts unoffered anonymous cipher suite, bypassing server authentication36Monitor
- CVE-2026-49759Stack buffer overflow in SCTP error cause parsing in inet_drv allows remote VM crash35Monitor
- CVE-2026-59251Denial of service via exponential certificate policy tree growth in path validation34Monitor
- CVE-2026-58227TLS/DTLS denial of service via unbounded recursion on cross-signed peer certificate chain34Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:erlang | 1:19.2.1+dfsg-2 · Debian:12 | Package registry (OSV) |
| suse:erlang | 18.3.4.7-9.1 · SUSE:Package Hub 12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.