Homepage

CVE-2026-70405 Affecting erlang package, versions <1:25.3.2.8+dfsg-1ubuntu4.7

Severity

 Recommended
medium

Based on Ubuntu security rating.

Threat Intelligence

EPSS
0.71% (52nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-UBUNTU2404-ERLANG-19519213
  • published28 Sept 2026
  • disclosed1 Sept 2026
Report a new vulnerability Found a mistake?

Introduced: 1 Sep 2026

CVE-2026-70405  (opens in a new tab)

How to fix?

Upgrade Ubuntu:24.04 erlang to version 1:25.3.2.8+dfsg-1ubuntu4.7 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream erlang package and not the erlang package as distributed by Ubuntu. See How to fix? for Ubuntu:24.04 relevant fixed versions and status.

Improper Validation of Specified Quantity in Input vulnerability in Erlang/OTP snmp allows a remote attacker to degrade availability by sending an SNMP message containing a BER INTEGER whose length field is arbitrarily large.

snmp_pdus:dec_integer_notag/1 defaults its size limit to infinity, and do_dec_integer_notag/2 then accumulates the value across every declared byte with a recursive shift and bitwise or. Work grows superlinearly in the declared length because each operation acts on a progressively larger bignum. The size-limited variant dec_integer_notag/2 exists but is reached from only one call site, dec_snmp_version/1, which bounds the version field to ten bytes; the request identifier, error status and index, generic and specific trap fields, engine boots and time, and every varbind value decoded by dec_value/1 all use the unbounded form. The decode runs before the PDU is processed, so no valid request is required beyond what the deployment demands to accept the message at all.

This issue affects OTP from OTP 17.0 before OTP 27.3.4.17, from OTP 28.0 before OTP 28.5.0.6, and from OTP 29.0 before OTP 29.0.6, corresponding to snmp from 4.25.1 before 5.18.2.1, from 5.19 before 5.20.2.2, and from 5.20.3 before 5.20.5. Whether OTP before OTP 17.0, corresponding to snmp before 4.25.1, is affected is unknown.