# CVE-2026-49760: Stack Buffer Overflow in ei_s_print_term at Very Large Integer

> A stack buffer overflow in Erlang OTP's erl_interface allows attackers to cause a denial of service via large integers.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jun 2026
- **Updated:** 24 Sep 2026
- **Also known as:** AZL-90114, DEBIAN-CVE-2026-49760, EEF-CVE-2026-49760, GHSA-xcxj-5pg2-v72j, UBUNTU-CVE-2026-49760

## What is CVE-2026-49760?

CVE-2026-49760 is a medium-severity memory corruption vulnerability in Erlang OTP, published on 10 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Stack-based Buffer Overflow vulnerability in Erlang OTP (erl_interface) allows Stack-based Buffer Overflow.

This vulnerability is associated with program file lib/erl_interface/src/misc/ei_printterm.c and program routine ei_s_print_term.

The C function ei_s_print_term uses an internal 2000-character stack buffer to format terms. When called with an encoded Erlang term containing a very large integer (encoded representation exceeding 2000 characters), the buffer overflows. The overflow bytes are restricted to the ASCII values of 0-9 and A-F, which limits exploitation to Denial of Service.

The companion function ei_print_term, which prints directly to a FILE instead of a memory buffer, does not contain this bug.

This issue affects OTP from OTP 17.0 before OTP 27.3.4.13, OTP 28.5.0.2, and OTP 29.0.2, corresponding to erl_interface from 3.7.16 before 5.5.2.1, 5.7.0.1, and 5.8.1. Whether OTP before OTP 17.0, corresponding to erl_interface before 3.7.16, is affected is unknown.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2026-49760?

It affects 2 products.


Products: Erlang Erl Interface, Erlang Erlang\/Otp.

## How do I fix CVE-2026-49760?

Upgrade to a fixed version.

## Is CVE-2026-49760 being exploited?

There is no known exploitation of CVE-2026-49760 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-49760 and fix it if it is affected.

What it is: CVE-2026-49760 is a medium-severity memory corruption vulnerability in Erlang OTP, published on 10 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-49760 in the wild and no public exploit code.

Affected product: Erlang OTP. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-49760/ (Markdown: https://insights.sbomify.com/CVE-2026-49760/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-49760
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-49760
- OSV: https://osv.dev/vulnerability/CVE-2026-49760

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-49760/
Summaries are generated and may contain mistakes; the official description above is the record.