CVE-2026-41429 Vulnerability Analysis & Exploit Details

CVE-2026-41429
Vulnerability Scoring

8.8
/10
Severe Risk

Cybersecurity professionals consider CVE-2026-41429 an immediate threat requiring urgent mitigation.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Adjacent_network
    Attack Vector Under Analysis
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-41429 Details

Status: Analyzed

Last updated: 🕕 05 May 2026, 18:12 UTC
Originally published on: 🕗 24 Apr 2026, 20:16 UTC

Time between publication and last update: 10 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVE-2026-41429 Vulnerability Summary

CVE-2026-41429: arduino-esp32 is an Arduino core for the ESP32, ESP32-S2, ESP32-S3, ESP32-C3, ESP32-C6 and ESP32-H2 microcontrollers. Prior to 3.3.8, there is a remotely reachable memory corruption issue in the NBNS packet handling path. When NetBIOS is enabled by calling NBNS.begin(...), the device listens on UDP port 137 and processes untrusted NBNS requests from the local network. The request parser trusts the attacker-controlled name_len field without enforcing a bound consistent with the fixed-size destination buffers used later in the flow. This vulnerability is fixed in 3.3.8.

Assessing the Risk of CVE-2026-41429

Access Complexity Graph

The exploitability of CVE-2026-41429 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-41429

With low attack complexity and no required privileges, CVE-2026-41429 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-41429, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-41429, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2026-41429 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2026-41429 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2026-41429 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2026-41429 References

External References

CWE Common Weakness Enumeration

CWE-121

Vulnerable Configurations

  • cpe:2.3:a:espressif:arduino-esp32:-:*:*:*:*:*:*:*
    cpe:2.3:a:espressif:arduino-esp32:-:*:*:*:*:*:*:*
  • cpe:2.3:a:espressif:arduino-esp32:1.0.0:-:*:*:*:*:*:*
    cpe:2.3:a:espressif:arduino-esp32:1.0.0:-:*:*:*:*:*:*
  • cpe:2.3:a:espressif:arduino-esp32:1.0.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:espressif:arduino-esp32:1.0.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:espressif:arduino-esp32:1.0.0:rc2:*:*:*:*:*:*
    cpe:2.3:a:espressif:arduino-esp32:1.0.0:rc2:*:*:*:*:*:*
  • cpe:2.3:a:espressif:arduino-esp32:1.0.0:rc3:*:*:*:*:*:*
    cpe:2.3:a:espressif:arduino-esp32:1.0.0:rc3:*:*:*:*:*:*
  • cpe:2.3:a:espressif:arduino-esp32:1.0.0:rc4:*:*:*:*:*:*
    cpe:2.3:a:espressif:arduino-esp32:1.0.0:rc4:*:*:*:*:*:*
  • cpe:2.3:a:espressif:arduino-esp32:1.0.1:-:*:*:*:*:*:*
    cpe:2.3:a:espressif:arduino-esp32:1.0.1:-:*:*:*:*:*:*
  • cpe:2.3:a:espressif:arduino-esp32:1.0.1:rc1:*:*:*:*:*:*
    cpe:2.3:a:espressif:arduino-esp32:1.0.1:rc1:*:*:*:*:*:*
  • cpe:2.3:a:espressif:arduino-esp32:1.0.1:rc2:*:*:*:*:*:*
    cpe:2.3:a:espressif:arduino-esp32:1.0.1:rc2:*:*:*:*:*:*
  • cpe:2.3:a:espressif:arduino-esp32:1.0.1:rc3:*:*:*:*:*:*
    cpe:2.3:a:espressif:arduino-esp32:1.0.1:rc3:*:*:*:*:*:*
  • cpe:2.3:a:espressif:arduino-esp32:1.0.1:rc4:*:*:*:*:*:*
    cpe:2.3:a:espressif:arduino-esp32:1.0.1:rc4:*:*:*:*:*:*
  • cpe:2.3:a:espressif:arduino-esp32:1.0.2:-:*:*:*:*:*:*
    cpe:2.3:a:espressif:arduino-esp32:1.0.2:-:*:*:*:*:*:*
  • cpe:2.3:a:espressif:arduino-esp32:1.0.2:rc1:*:*:*:*:*:*
    cpe:2.3:a:espressif:arduino-esp32:1.0.2:rc1:*:*:*:*:*:*
  • cpe:2.3:a:espressif:arduino-esp32:1.0.2:rc2:*:*:*:*:*:*
    cpe:2.3:a:espressif:arduino-esp32:1.0.2:rc2:*:*:*:*:*:*
  • cpe:2.3:a:espressif:arduino-esp32:1.0.3:-:*:*:*:*:*:*
    cpe:2.3:a:espressif:arduino-esp32:1.0.3:-:*:*:*:*:*:*
  • cpe:2.3:a:espressif:arduino-esp32:1.0.3:rc1:*:*:*:*:*:*
    cpe:2.3:a:espressif:arduino-esp32:1.0.3:rc1:*:*:*:*:*:*
  • cpe:2.3:a:espressif:arduino-esp32:1.0.3:rc2:*:*:*:*:*:*
    cpe:2.3:a:espressif:arduino-esp32:1.0.3:rc2:*:*:*:*:*:*
  • cpe:2.3:h:espressif:esp32:-:*:*:*:*:*:*:*
    cpe:2.3:h:espressif:esp32:-:*:*:*:*:*:*:*
  • cpe:2.3:h:espressif:esp32-c3:-:*:*:*:*:*:*:*
    cpe:2.3:h:espressif:esp32-c3:-:*:*:*:*:*:*:*
  • cpe:2.3:h:espressif:esp32-c6:-:*:*:*:*:*:*:*
    cpe:2.3:h:espressif:esp32-c6:-:*:*:*:*:*:*:*
  • cpe:2.3:h:espressif:esp32-h2:-:*:*:*:*:*:*:*
    cpe:2.3:h:espressif:esp32-h2:-:*:*:*:*:*:*:*
  • cpe:2.3:h:espressif:esp32-s2:-:*:*:*:*:*:*:*
    cpe:2.3:h:espressif:esp32-s2:-:*:*:*:*:*:*:*
  • cpe:2.3:h:espressif:esp32-s3:-:*:*:*:*:*:*:*
    cpe:2.3:h:espressif:esp32-s3:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-41429: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-8288 – A vulnerability was determined in Open5GS up to 2.7.7. This affects the function gsm_handle_pdu_session_modification_qos_flow_descriptions of the f...
  • CVE-2025-9973 – Due to not validating the organization context when executing adaptive authentication flows, the WSO2 Identity Server allows adaptive authenticatio...
  • CVE-2025-10470 – The Magic Link authentication flow accepts multiple invalid authentication requests without adequate rate limiting or resource control, leading to ...
  • CVE-2026-6956 – ATutor is vulnerable to Reflected XSS in /install/install.php endpoint. An attacker can provide a specially crafted URL that, when opened, results ...
  • CVE-2026-6909 – ATutor is vulnerable to Reflected XSS in /install/upgrade.php endpoint. An attacker can provide a specially crafted URL that, when opened, results ...