OESA-2026-4255 (CVE-2026-65634)
Vulnerability from osv_openeuler – Published: 2026-10-16 11:58 – Updated: 2026-10-16 11:58 – Source websiteErlang is a general-purpose programming language and runtime environment. Erlang has built-in support for concurrency, distribution and fault tolerance. Erlang is used in several large telecommunication systems from Ericsson.
Security Fix(es):
Inefficient algorithmic complexity in the Erlang/OTP asn1 OBJECT IDENTIFIER decoder allows a remote unauthenticated attacker to cause denial of service by sending a crafted OID during the TLS handshake.
The BER OID decoder asn1rtt_ber:dec_subidentifiers/3 in lib/asn1/src/asn1rtt_ber.erl and the equivalent PER helper asn1rtt_per_common:dec_subidentifiers/3 in lib/asn1/src/asn1rtt_per_common.erl accumulate a base-128 subidentifier into an unbounded integer using (Av bsl 7) + H per continuation byte. Each shift and addition on the growing accumulator is linear in the number of bits already accumulated, giving quadratic total work in the size of a single subidentifier. The JER helper asn1rtt_jer:json2oid/1 in lib/asn1/src/asn1rtt_jer.erl exhibits the same class of unbounded-integer parsing when decoding a dot-separated OID from JSON. A DER-encoded OBJECT IDENTIFIER with one very large arc (approximately 262 KB of continuation bytes) consumes roughly 13 seconds of CPU on typical hardware.
The vulnerable decoder is generated into every ASN.1 module that contains an OBJECT IDENTIFIER, including OTP-PUB-KEY which is reached during X.509 certificate parsing via public_key:pkix_decode_cert/2. This decoder runs before any signature or trust chain verification, so any Erlang service that parses peer TLS certificates is exposed: the default for TLS clients (which always parse the server certificate) and for mutual-TLS servers (which parse client certificates).
This vulnerability is associated with program files lib/asn1/src/asn1rtt_ber.erl, lib/asn1/src/asn1rtt_per_common.erl and lib/asn1/src/asn1rtt_jer.erl and program routines asn1rtt_ber:dec_subidentifiers/3, asn1rtt_per_common:dec_subidentifiers/3 and asn1rtt_jer:json2oid/1.
This issue affects OTP from OTP 17.0 before OTP 27.3.4.18, OTP 28.5.0.7, and OTP 29.1.1, corresponding to asn1 from 3.0 before 5.3.4.3, 5.4.3.1, and 5.5.2. Whether OTP before OTP 17.0, corresponding to asn1 before 3.0, is affected is unknown.(CVE-2026-65634)
Allocation of Resources Without Limits or Throttling vulnerability in Erlang/OTP ssh allows an authenticated remote attacker to exhaust node memory by repeatedly opening session channels that are never assigned a handler.
The "session" clause of ssh_connection:handle_msg/4 checks only minimal_remote_max_packet_size before calling setup_session/5, which unconditionally builds a #channel{} record and stores it in the ETS channel cache. The max_channels daemon option is consulted only by ssh_channel_sup:max_num_channels_not_exceeded/2, which counts supervisor children, so a channel that never gets a shell, exec, or subsystem handler is invisible to the limit and setting the option to a finite value does not mitigate the attack. RFC 4254 section 5.1 permits many session channels per connection, and each record costs only a few hundred bytes, so a single authenticated connection can accumulate channels until the node runs out of memory and the emulator terminates, affecting every application on it. No file contents, credentials, or write access are obtainable.
This issue affects OTP from OTP 18.1.2 before OTP 27.3.4.18, OTP 28.5.0.7, and OTP 29.1.1, corresponding to ssh from 4.1.1 before 5.2.11.13, 5.5.2.6, and 6.0.6. Whether OTP before OTP 18.1.2, corresponding to ssh before 4.1.1, is affected is unknown.(CVE-2026-68956)
Key Exchange without Entity Authentication vulnerability in Erlang/OTP ssl allows a peer that answers a TLS 1.3 client connection to impersonate the intended server. A pre_shared_key extension in the ServerHello that the client never offered causes the client to complete the handshake without validating the server's certificate, so ssl:connect returns {ok, Socket} against a peer holding no certificate, no private key and no prior session.
tls_client_connection_1_3:handle_server_hello/2 passes the received extension to tls_gen_connection_1_3:handle_resumption/2, which sets resumption = true on its mere presence without checking that the client offered a PSK. tls_handshake_1_3:get_pre_shared_key/4 meanwhile falls back to the all-zero "no PSK" value and keys the handshake with the ordinary non-PSK schedule, so the attacker's own ephemeral key suffices. The resumption flag then routes maybe_resumption/1 straight to wait_finished, skipping the certificate-handling states, so certificate path validation, verify_fun, hostname verification, partial_chain, CRL checking and OCSP stapling are all bypassed. The default client configuration is affected; clients restricted to TLS 1.2 are not.
This issue affects OTP from OTP 22.2 before OTP 27.3.4.18, OTP 28.5.0.7, and OTP 29.1.1, corresponding to ssl from 9.5 before 11.2.12.13, 11.6.0.6, and 11.7.7.(CVE-2026-89422)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"erlang-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-asn1-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-common_test-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-compiler-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-crypto-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-debugger-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-debuginfo-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-debugsource-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-dialyzer-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-diameter-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-edoc-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-eldap-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-erl_docgen-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-erl_interface-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-erts-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-et-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-eunit-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-examples-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-ftp-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-inets-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-jinterface-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-kernel-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-megaco-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-mnesia-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-observer-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-odbc-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-os_mon-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-parsetools-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-public_key-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-reltool-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-runtime_tools-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-sasl-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-snmp-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-src-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-ssh-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-ssl-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-stdlib-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-syntax_tools-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-tftp-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-tools-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-wx-25.3.2.6-21.oe2403sp1.aarch64.rpm",
"erlang-xmerl-25.3.2.6-21.oe2403sp1.aarch64.rpm"
],
"src": [
"erlang-25.3.2.6-21.oe2403sp1.src.rpm"
],
"x86_64": [
"erlang-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-asn1-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-common_test-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-compiler-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-crypto-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-debugger-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-debuginfo-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-debugsource-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-dialyzer-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-diameter-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-edoc-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-eldap-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-erl_docgen-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-erl_interface-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-erts-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-et-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-eunit-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-examples-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-ftp-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-inets-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-jinterface-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-kernel-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-megaco-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-mnesia-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-observer-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-odbc-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-os_mon-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-parsetools-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-public_key-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-reltool-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-runtime_tools-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-sasl-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-snmp-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-src-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-ssh-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-ssl-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-stdlib-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-syntax_tools-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-tftp-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-tools-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-wx-25.3.2.6-21.oe2403sp1.x86_64.rpm",
"erlang-xmerl-25.3.2.6-21.oe2403sp1.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:24.03-LTS-SP1",
"name": "erlang",
"purl": "pkg:rpm/openEuler/erlang\u0026distro=openEuler-24.03-LTS-SP1"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "25.3.2.6-21.oe2403sp1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "Critical"
},
"details": "Erlang is a general-purpose programming language and runtime environment. Erlang has built-in support for concurrency, distribution and fault tolerance. Erlang is used in several large telecommunication systems from Ericsson.\r\n\r\nSecurity Fix(es):\n\nInefficient algorithmic complexity in the Erlang/OTP asn1 OBJECT IDENTIFIER decoder allows a remote unauthenticated attacker to cause denial of service by sending a crafted OID during the TLS handshake.\n\nThe BER OID decoder asn1rtt_ber:dec_subidentifiers/3 in lib/asn1/src/asn1rtt_ber.erl and the equivalent PER helper asn1rtt_per_common:dec_subidentifiers/3 in lib/asn1/src/asn1rtt_per_common.erl accumulate a base-128 subidentifier into an unbounded integer using (Av bsl 7) + H per continuation byte. Each shift and addition on the growing accumulator is linear in the number of bits already accumulated, giving quadratic total work in the size of a single subidentifier. The JER helper asn1rtt_jer:json2oid/1 in lib/asn1/src/asn1rtt_jer.erl exhibits the same class of unbounded-integer parsing when decoding a dot-separated OID from JSON. A DER-encoded OBJECT IDENTIFIER with one very large arc (approximately 262 KB of continuation bytes) consumes roughly 13 seconds of CPU on typical hardware.\n\nThe vulnerable decoder is generated into every ASN.1 module that contains an OBJECT IDENTIFIER, including OTP-PUB-KEY which is reached during X.509 certificate parsing via public_key:pkix_decode_cert/2. This decoder runs before any signature or trust chain verification, so any Erlang service that parses peer TLS certificates is exposed: the default for TLS clients (which always parse the server certificate) and for mutual-TLS servers (which parse client certificates).\n\nThis vulnerability is associated with program files lib/asn1/src/asn1rtt_ber.erl, lib/asn1/src/asn1rtt_per_common.erl and lib/asn1/src/asn1rtt_jer.erl and program routines asn1rtt_ber:dec_subidentifiers/3, asn1rtt_per_common:dec_subidentifiers/3 and asn1rtt_jer:json2oid/1.\n\nThis issue affects OTP from OTP\u00a017.0 before OTP\u00a027.3.4.18, OTP\u00a028.5.0.7, and OTP\u00a029.1.1, corresponding to asn1 from 3.0 before 5.3.4.3, 5.4.3.1, and 5.5.2. Whether OTP before OTP\u00a017.0, corresponding to asn1 before 3.0, is affected is unknown.(CVE-2026-65634)\n\nAllocation of Resources Without Limits or Throttling vulnerability in Erlang/OTP ssh allows an authenticated remote attacker to exhaust node memory by repeatedly opening session channels that are never assigned a handler.\n\nThe \u0026quot;session\u0026quot; clause of ssh_connection:handle_msg/4 checks only minimal_remote_max_packet_size before calling setup_session/5, which unconditionally builds a #channel{} record and stores it in the ETS channel cache. The max_channels daemon option is consulted only by ssh_channel_sup:max_num_channels_not_exceeded/2, which counts supervisor children, so a channel that never gets a shell, exec, or subsystem handler is invisible to the limit and setting the option to a finite value does not mitigate the attack. RFC 4254 section 5.1 permits many session channels per connection, and each record costs only a few hundred bytes, so a single authenticated connection can accumulate channels until the node runs out of memory and the emulator terminates, affecting every application on it. No file contents, credentials, or write access are obtainable.\n\nThis issue affects OTP from OTP\u00a018.1.2 before OTP\u00a027.3.4.18, OTP\u00a028.5.0.7, and OTP\u00a029.1.1, corresponding to ssh from 4.1.1 before 5.2.11.13, 5.5.2.6, and 6.0.6. Whether OTP before OTP\u00a018.1.2, corresponding to ssh before 4.1.1, is affected is unknown.(CVE-2026-68956)\n\nKey Exchange without Entity Authentication vulnerability in Erlang/OTP ssl allows a peer that answers a TLS 1.3 client connection to impersonate the intended server. A pre_shared_key extension in the ServerHello that the client never offered causes the client to complete the handshake without validating the server\u0026apos;s certificate, so ssl:connect returns {ok, Socket} against a peer holding no certificate, no private key and no prior session.\n\ntls_client_connection_1_3:handle_server_hello/2 passes the received extension to tls_gen_connection_1_3:handle_resumption/2, which sets resumption = true on its mere presence without checking that the client offered a PSK. tls_handshake_1_3:get_pre_shared_key/4 meanwhile falls back to the all-zero \u0026quot;no PSK\u0026quot; value and keys the handshake with the ordinary non-PSK schedule, so the attacker\u0026apos;s own ephemeral key suffices. The resumption flag then routes maybe_resumption/1 straight to wait_finished, skipping the certificate-handling states, so certificate path validation, verify_fun, hostname verification, partial_chain, CRL checking and OCSP stapling are all bypassed. The default client configuration is affected; clients restricted to TLS 1.2 are not.\n\nThis issue affects OTP from OTP\u00a022.2 before OTP\u00a027.3.4.18, OTP\u00a028.5.0.7, and OTP\u00a029.1.1, corresponding to ssl from 9.5 before 11.2.12.13, 11.6.0.6, and 11.7.7.(CVE-2026-89422)",
"id": "OESA-2026-4255",
"modified": "2026-10-16T11:58:39Z",
"published": "2026-10-16T11:58:39Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-4255"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-65634"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-68956"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89422"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "erlang security update",
"upstream": [
"CVE-2026-65634",
"CVE-2026-68956",
"CVE-2026-89422"
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.