CVE-2026-79981

MEDIUM CVSS 6.5
Published: 2026-10-23
Modified: 2026-10-23
Enriched via mock
Tenable Plugin

Checking the public Tenable catalog…

AI Threat Summary

CVE-2026-79981 is a moderate vulnerability with a CVSS score of 6.5 affecting the target software. Threat hunters should monitor for exploit attempts and apply vendor patches immediately.

Description

The DNS stub resolver in subsys/net/lib/dns/resolve.c binds one UDP socket per configured server when the resolver context is initialised (dns_resolve_init_locked() -> register_dispatcher() -> dns_dispatcher_register()), with the local port left at 0 so the stack picks an ephemeral port exactly once. dns_write() then sends every subsequent query from that same socket without re-binding, so the source port is constant for the lifetime of the resolver context while only the 16-bit transaction identifier (ctx->queries[i].id, drawn with sys_rand16_get()) varies per query. RFC 5452 section 9.2 requires both to vary; with a fixed port, an off-path attacker has to guess only the identifier. The stable port is cheap to learn. Any single observed query reveals it permanently, and it can also be found by probing the ephemeral UDP range: subsys/net/ip/connection.c answers unmatched unicast UDP with an ICMP port-unreachable, so the resolver's socket is the one port in that range that stays silent. Acceptance of a reply is decided solely by get_slot_by_id() matching the transaction identifier and a CRC-16 of the queried name — the reply's source address is never checked (dispatcher_cb() does ARG_UNUSED(addr)), so forged answers need not even be spoofed to appear to come from the configured server; they only need to reach the resolver's port. An attacker with UDP reachability to the device (same LAN, Wi-Fi or mesh segment, or a globally routable device address) can therefore flood answers for a predictable query name across the 16-bit identifier space during a query window and race the legitimate server. A win makes the application resolve an attacker-chosen address, and with CONFIG_DNS_RESOLVER_CACHE enabled the forged record is retained for its attacker-chosen TTL. The attack still requires winning that race, and applications that validate TLS certificates for the resolved endpoint are largely protected. The fix draws a fresh local port before each query to a server that has nothing outstanding: dns_randomize_source_port() unregisters the dispatcher, closes and reopens the socket, and re-registers it bound to port 0 so the system selects a new port, raising the per-query guessing space from roughly 16 to roughly 31 bits. Multicast DNS and LLMNR are excluded because their ports are protocol-fixed. The behaviour is controlled by CONFIG_DNS_RESOLVER_RANDOMIZE_SOURCE_PORT (default y).

Attack Chain
1
Reconnaissance

Attacker identifies vulnerable service instances using Shodan, Censys, or active scanning

2
Initial Access

Attacker crafts malicious payload exploiting CVE-2026-79981 to achieve remote code execution

3
Execution

Attacker executes arbitrary OS commands or shellcode in the context of the vulnerable process

4
Persistence

Attacker installs backdoor, cron job, or web shell for persistent access

5
Lateral Movement

Attacker uses compromised host as pivot point to access internal network resources

MITRE ATT&CK Techniques
T1190 Exploit Public-Facing Application
Initial Access

Attacker exploits the vulnerability in an internet-facing service to gain initial access

T1059 Command and Scripting Interpreter
Execution

Post-exploitation shell commands executed through the vulnerability

T1105 Ingress Tool Transfer
Command and Control

Attacker downloads malware or tools after gaining code execution

Indicators of Compromise
Type Value Description
user_agent Mozilla/5.0 (compatible; exploit/1.0) Generic exploit scanner user agent pattern
url /api/vuln-endpoint?payload=<malicious> Exploit attempt against application endpoint — monitor access logs for anomalous params
registry_key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\backdoor Persistence mechanism after successful RCE
Remediation
1. Apply vendor-supplied security patches immediately. 2. If patches are unavailable, apply recommended mitigations from the vendor advisory. 3. Enable WAF rules or IDS signatures to detect exploitation attempts. 4. Monitor logs for indicators of compromise listed above. 5. Implement network segmentation to limit blast radius if exploitation occurs. 6. Subscribe to vendor security advisories for this product.
Quick Facts
CVE ID CVE-2026-79981
CVSS Score 6.5
Vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N
Published 2026-10-23
Exploited No
CISA KEV No
PoC Not public