Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-103936 Overview
CVE-2026-103936 is a denial-of-service vulnerability in @libp2p/webrtc, the WebRTC transport for the JavaScript implementation of libp2p. Versions prior to 6.0.28 process unauthenticated STUN Binding Requests before any peer authentication, Noise handshake, or connection admission occurs. A remote attacker can send a single crafted UDP packet containing a short ufrag value to abort the Node.js listener process. The flaw is tracked as an unchecked exception issue [CWE-248] and is fixed in 6.0.28.
Critical Impact
A single unauthenticated UDP packet terminates the Node.js listener with SIGABRT, enabling trivial remote denial of service against any libp2p node exposing webRTCDirect().
Affected Products
- @libp2p/webrtc versions prior to 6.0.28
- js-libp2p nodes exposing the webRTCDirect() Node.js listener
- Deployments using node-datachannel or libdatachannel as the underlying ICE/DTLS stack
Discovery Timeline
- 2026-10-15 - CVE-2026-103936 published to NVD
- 2026-10-16 - Last updated in NVD database
Technical Details for CVE-2026-103936
Vulnerability Analysis
The vulnerability resides in the webRTCDirect() listener implemented in packages/transport-webrtc/src/private-to-public/utils/stun-listener.ts. When a STUN Binding Request arrives, the listener extracts the attacker-controlled request.ufrag field and forwards it directly into DirectRTCPeerConnection.setLocalDescription. The value is then reused as the ICE password without validation of length or allowed character set.
STUN processing occurs before PeerId authentication, Noise encryption, stream multiplexing, protocol negotiation, connection creation, and connection-manager admission. No authentication state exists at the point of failure. When the invalid ufrag reaches the native backing library (node-datachannel or libdatachannel), the C++ layer raises an uncaught invalid_argument exception. Node.js cannot catch this native exception, so the process aborts with SIGABRT.
Confirmed impact is limited to process termination. Researchers did not demonstrate memory corruption, remote code execution, confidentiality or integrity loss, browser-side impact, or connection-limit bypass.
Root Cause
The root cause is missing input validation on a protocol-controlled field combined with an unhandled native exception [CWE-248]. ICE credentials have required minimum lengths and a restricted character set per RFC 8445. The listener trusted the remote value and passed it through to a native call that enforces those requirements by throwing, rather than returning an error that JavaScript can handle.
Attack Vector
Exploitation requires only network reach to the listener's UDP port. The attacker sends one STUN Binding Request with a ufrag attribute shorter than the ICE specification allows. No prior session, authentication, or handshake is needed. The listener process terminates immediately, denying service to all peers connected through that node.
// Patch excerpt - packages/transport-webrtc/src/private-to-public/utils/get-rtcpeerconnection.ts
+import { InvalidParametersError } from '@libp2p/interface'
import { Crypto } from '@peculiar/webcrypto'
import { PeerConnection } from 'node-datachannel'
import { RTCPeerConnection } from 'node-datachannel/polyfill'
import { DEFAULT_ICE_SERVERS, MAX_MESSAGE_SIZE } from '../../constants.ts'
import { DataChannelMuxerFactory } from '../../muxer.ts'
+import { isValidUfrag } from '../../util.ts'
import { generateTransportCertificate } from './generate-certificates.ts'
// Patch excerpt - packages/transport-webrtc/src/private-to-public/utils/stun-listener.ts
import { isIPv4 } from '@chainsafe/is-ip'
import { IceUdpMuxListener } from 'node-datachannel'
+import { handleStunRequest } from '../../util.ts'
import type { Logger } from '@libp2p/interface'
// Source: https://github.com/libp2p/js-libp2p/commit/68794c8e2e67d5f38da59e379dc051b2789e46f6
The patch introduces an isValidUfrag helper and routes incoming STUN requests through a handleStunRequest wrapper that rejects malformed credentials before the value reaches the native layer.
Detection Methods for CVE-2026-103936
Indicators of Compromise
- Unexpected SIGABRT termination of Node.js processes running js-libp2p with the WebRTC Direct transport enabled.
- Native stack traces referencing node-datachannel, libdatachannel, or an uncaught invalid_argument exception immediately following inbound UDP traffic.
- Inbound STUN Binding Requests containing USERNAME/ufrag attributes shorter than four characters or containing characters outside the ICE allowed set.
Detection Strategies
- Inspect UDP traffic on listener ports for STUN packets (magic cookie 0x2112A442) and flag Binding Requests with undersized ufrag attributes.
- Correlate process-exit telemetry on libp2p hosts with inbound WebRTC traffic volume to identify crash-on-packet patterns.
- Alert when a long-running libp2p Node.js process restarts repeatedly within short windows following remote connectivity attempts.
Monitoring Recommendations
- Enable process supervisor logs (systemd, PM2, Kubernetes) to capture SIGABRT exit codes and timestamps.
- Forward native crash logs and Node.js stderr to a centralized logging platform for correlation with network flow data.
- Monitor the installed version of @libp2p/webrtc across the fleet to confirm 6.0.28 or later is deployed.
How to Mitigate CVE-2026-103936
Immediate Actions Required
- Upgrade @libp2p/webrtc to version 6.0.28 or later across all Node.js listeners.
- Audit dependency trees for transitive uses of vulnerable @libp2p/webrtc versions and rebuild affected services.
- Restart affected services after upgrade to ensure the patched listener is active.
Patch Information
The fix is published in the webrtc-v6.0.28 release and merged via Pull Request #3584. Full details are available in GitHub Security Advisory GHSA-x3m2-6mg8-vj7f and the upstream commit.
Workarounds
- Disable the webRTCDirect() listener on untrusted interfaces until the patched version is deployed.
- Restrict UDP access to the WebRTC Direct listener port using firewall rules that limit sources to known peers.
- Run libp2p nodes under a supervisor that auto-restarts on SIGABRT to reduce the duration of outage during exploitation.
# Upgrade to the patched @libp2p/webrtc release
npm install @libp2p/webrtc@^6.0.28
# Verify the installed version
npm ls @libp2p/webrtc
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

