☠️
EXFILTRATING
DATA...
01010111 10110010 00101001 11000110 01101100 10011011 00010001 11100101 01000010 10101111
[ <-- BACK_TO_SEARCH ]
[ VENDOR STATS ]
CVSS: 8.8 CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H 🐛 CWE-122
👁️
Common Weakness Enumeration - Identifies the specific category of software weakness or flaw.

CVE-2026-103994

CVE-2026-103994 Heap Buffer Overflow in Juniper
📅 PUBLISHED: 2026-10-14 00:00 UTC 🔄 UPDATED: 2026-10-15 05:00 UTC
[ ZERO-DAY / UNPATCHED ] [ DEFENSE PATCH ↓ ]
💣 PoC: None
👁️
Proof of Concept - Indicates if functional exploit code is publicly available, drastically increasing the risk of immediate attacks.
🥷 MITRE: T1190
👁️
MITRE ATT&CK Tactic - Describes the strategy hackers use to execute this attack.
VULNERABLE: Junos OS (versions containing the VXLAN Gateway Daemon are affected; exact ranges not specified in provided data)
CVSS VECTOR BREAKDOWN 8.8
AV: A Attack Vector Adjacent
AC: L Attack Complexity Low
PR: N Privileges Required None
UI: N User Interaction None
S: U Scope Unchanged
C: H Confidentiality High
I: H Integrity High
A: H Availability High
8.8
THREAT LEVEL
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

CVE-2026-103994 is a heap-based buffer overflow vulnerability in the VXLAN Gateway Daemon (vgd) of Juniper Networks Junos OS. It allows a malicious or compromised SDN controller to cause a complete outage of the OVSDB control plane and potentially achieve remote code execution. The vulnerability carries a CVSS score of 8.8, making it a high-severity issue that demands immediate attention from organizations using Junos OS in SDN-controlled environments.

⚡ AUTOMATE YOUR CVE INTELLIGENCE

This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.

›Patch confidence — UNVERIFIED to CONFIRMED, cross-referenced NVD + RHSA + Debian
›Exploit & PoC — poc_status, poc_url, has_exploit. Not in NVD.
›Shodan dorks — ready-made queries to find exposed vulnerable systems
›Detection rules — YARA · Wazuh · Elastic (all plans) · Sigma (Pro)
›pending_fields — know exactly which of 7 fields NVD hasn't processed yet
›Free backfill — data incomplete when you paid? Re-check within 30 days = 0 credits
PAYG €0.08/lookup Standard €19/mo (was €29) · 5k credits Pro €65/mo (was €99) · 20k credits FOUNDING PRICE · LOCKED FOR LIFE · ENDS 31 DEC 2026
[ FROM €19/MO ]
Free sandbox key available
No signup required

Technical Analysis

The vulnerability resides in the VXLAN Gateway Daemon, a component responsible for managing VXLAN tunnels and interacting with the OVSDB (Open vSwitch Database) control plane. The flaw is classified as CWE-122 (Heap-based Buffer Overflow), which occurs when a program writes more data to a buffer allocated on the heap than it can hold. In this specific case, the overflow is triggered by input from a malicious or compromised SDN controller. The SDN controller communicates with the vgd process through the OVSDB protocol, and specially crafted messages can cause a buffer overflow condition.

The attack vector is adjacent network (AV:A), meaning the attacker must be on the same layer-2 network segment or have access to the SDN control plane. The attack complexity is low (AC:L), no privileges are required (PR:N), and no user interaction is needed (UI:N). Successful exploitation leads to high confidentiality, integrity, and availability impacts (C:H/I:H/A:H). The heap-based buffer overflow can result in memory corruption, which may allow an attacker to execute arbitrary code in the context of the vgd process, or at minimum, crash the daemon and cause a denial of service on the OVSDB control plane.

Because the vulnerability is in the control plane management daemon, exploitation could disrupt the entire VXLAN overlay network, affecting all tenant traffic and connectivity. The SDN controller is a trusted component in the network architecture, so a compromised controller can send malformed OVSDB messages that the vgd process fails to validate properly. The lack of a published patch or workaround further increases the risk.

Exploitation Scenarios

Reconnaissance/Target Identification: An attacker first identifies a Juniper Networks device running Junos OS with the VXLAN Gateway Daemon enabled and managed by an SDN controller. This could be done through network scanning for OVSDB ports (typically TCP 6632 or 6640) or by compromising an existing SDN controller.

Triggering the Flaw: The attacker, acting as or through a malicious SDN controller, sends a crafted OVSDB protocol message to the vgd process on the target device. The message contains an oversized or malformed field that causes the heap-based buffer overflow. No authentication is required from the controller, as the daemon trusts the control plane.

Payload/Execution: The overflow overwrites adjacent heap memory. Depending on the exact memory layout, the attacker may be able to control execution flow and inject shellcode or ROP gadgets to achieve remote code execution. If RCE is not achieved, the overflow will at least crash the daemon, causing a complete outage of the OVSDB control plane.

Post-Exploitation Impact: Successful RCE grants the attacker the ability to execute commands with the privileges of the vgd process (likely root or a high-privilege user). This could lead to full device compromise, persistent backdoor installation, traffic interception, or further lateral movement within the network. Even without RCE, the DoS condition disrupts all VXLAN overlay services, impacting tenant connectivity and business operations.

No public proof-of-concept or exploit code is available. The attack chain is inferred from the vulnerability class and the description provided.

Impact Assessment

The CVSS v3.1 score of 8.8 reflects the high severity of this vulnerability. The adjacent network attack vector means an attacker must have access to the SDN control plane, but no authentication or user interaction is needed. The high confidentiality, integrity, and availability impacts indicate that a successful exploit could lead to complete loss of data confidentiality, integrity, and system availability. In a service provider or large enterprise environment, this could result in widespread network outages, data breaches, and disruption of critical services. The blast radius includes all devices managed by the affected SDN controller and all tenants relying on the VXLAN overlay.

Detection Guidance

Sigma Rule

title: Juniper Junos VXLAN Gateway Daemon Heap Overflow Exploitation Attempt
id: 8a4f3c2e-1b5d-4e7f-9a0c-3d6e8f2a1b4c
status: experimental
description: Detects potential exploitation of CVE-2026-103994 via OVSDB traffic to the VXLAN Gateway Daemon
author: Threat Intelligence Team
date: 2026-01-01
logsource:
    category: network_flow
    product: suricata
detection:
    selection:
        dest_port: 6632
        flowbytes_sent: 
            - '>5000'
    condition: selection
falsepositives:
    - Legitimate OVSDB traffic with large payloads
level: high
tags:
    - attack.t1190
    - cve.2026.103994

YARA Rule

rule CVE_2026_103994_Juniper_vgd_HeapOverflow
{
    meta:
        description = "Detects potential heap-based buffer overflow exploitation in Juniper Junos VXLAN Gateway Daemon (vgd)"
        author = "Threat Intelligence Team"
        date = "2026-01-01"
        reference = "CVE-2026-103994"
        severity = "high"
    strings:
        $ovsdb_header = { 00 00 00 00 } // OVSDB JSON-RPC header placeholder
        $oversized_json = /"method"\s*:\s*"[^"]{500,}"/
        $vgd_process = "vgd" ascii wide nocase
    condition:
        uint32(0) == 0x00000000 and $oversized_json and $vgd_process
}

Suricata IDS Rule

alert tcp any any -> any 6632 (msg:"CVE-2026-103994 Juniper Junos VXLAN Gateway Daemon Heap Overflow Attempt"; flow:to_server,established; content:"|00 00 00 00|"; depth:4; content:"method"; nocase; content:"params"; nocase; byte_test:4,>,4096,0,relative; classtype:attempted-admin; sid:10000001; rev:1; reference:cve,2026-103994;)

Elastic Detection

network where destination.port == 6632 and network.bytes > 5000 and event.action == "network_flow"

Splunk SPL Query

index=network sourcetype=ovsdb OR sourcetype=junos
| search dest_port=6632
| stats sum(bytes) as total_bytes by src_ip, dest_ip
| where total_bytes > 5000
| table src_ip, dest_ip, total_bytes

Wazuh OSSEC Rule

<group name="junos,cve-2026-103994,">
  <rule id="100001" level="12">
    <decoded_as>json</decoded_as>
    <field name="dest_port">6632</field>
    <field name="bytes">\.{5,}</field>
    <description>CVE-2026-103994: Potential heap overflow in Juniper Junos VXLAN Gateway Daemon</description>
    <mitre>
      <id>T1190</id>
    </mitre>
  </rule>
</group>

Mitigation & Patch Guidance

Patch confidence: 0/4 (UNPATCHED — no patch evidence from any tracked source).

  1. Immediate Mitigations: Restrict access to the OVSDB control plane to trusted SDN controllers only. Implement network segmentation to isolate the VXLAN Gateway Daemon from untrusted networks. Monitor for anomalous OVSDB traffic, especially oversized or malformed messages. If possible, disable the VXLAN Gateway Daemon if not required for operations.

  2. Patch/Upgrade Steps: No vendor patch is currently available. Monitor Juniper Networks security advisories for updates. Once a patch is released, apply it immediately following standard change management procedures. Test in a non-production environment first.

  3. Long-term Hardening: Implement strict input validation on all OVSDB messages, though this may require vendor involvement. Use secure SDN controller authentication and authorization mechanisms. Deploy network intrusion detection systems with rules tailored to OVSDB protocol anomalies. Regularly audit and update Junos OS to the latest available version. Consider using hardware-based memory protection mechanisms if supported.

References

  1. NVD Entry: https://nvd.nist.gov/vuln/detail/CVE-2026-103994
  2. Juniper Networks Security Advisories: https://supportportal.juniper.net/s/global-search/%40uri#q=CVE-2026-103994
  3. CWE-122: Heap-based Buffer Overflow: https://cwe.mitre.org/data/definitions/122.html
  4. MITRE ATT&CK T1190: https://attack.mitre.org/techniques/T1190/
  5. CISA KEV Catalog: Not applicable (CVE not listed as of report date)

No known threat actor campaigns or exploit-in-the-wild evidence are available at this time.

👁️ SHODAN DORKS (THREAT HUNTING)

What is this? Security researchers use these exact search queries on Shodan.io (a search engine for internet-connected devices) to find vulnerable systems globally. You can copy these dorks to see if your organization's IP space is exposed.

product:"Juniper"
title:"Juniper"
◈ SOURCE Analysis & enrichment: valtersit.com/cve/CVE-2026-103994/ · CVE data: NVD/MITRE (public domain) · © 2026 ValtersIT Hub
>_ SYSTEM_CORE: INTEL_ACTIVE
90% TEAM-CURATED // 10% AUTOMATED INGESTION.
ALL PATCH REFERENCES AND VERSION DATA SOURCED FROM NVD + OSV OFFICIAL REGISTRIES.