CVE-2025-55292 Vulnerability Analysis & Exploit Details

CVE-2025-55292
Vulnerability Scoring

8.2
/10
Severe Risk

Cybersecurity professionals consider CVE-2025-55292 an immediate threat requiring urgent mitigation.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • 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-2025-55292 Details

Status: Analyzed

Last updated: 🕘 02 Mar 2026, 21:17 UTC
Originally published on: 🕛 28 Jan 2026, 00:15 UTC

Time between publication and last update: 33 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2025-55292 Vulnerability Summary

CVE-2025-55292: Meshtastic is an open source mesh networking solution. In the current Meshtastic architecture, a Node is identified by their NodeID, generated from the MAC address, rather than their public key. This aspect downgrades the security, specifically by abusing the HAM mode which doesn't use encryption. An attacker can, as such, forge a NodeInfo on behalf of a victim node advertising that the HAM mode is enabled. This, in turn, will allow the other nodes on the mesh to accept the new information and overwriting the NodeDB. The other nodes will then only be able to send direct messages to the victim by using the shared channel key instead of the PKC. Additionally, because HAM mode by design doesn't provide any confidentiality or authentication of information, the attacker could potentially also be able to change the Node details, like the full name, short code, etc. To keep the attack persistent, it is enough to regularly resend the forged NodeInfo, in particular right after the victim sends their own. A patch is available in version 2.7.6.834c3c5.

Assessing the Risk of CVE-2025-55292

Access Complexity Graph

The exploitability of CVE-2025-55292 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-2025-55292

With low attack complexity and no required privileges, CVE-2025-55292 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-2025-55292, 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-2025-55292, 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-2025-55292 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: Low
    Exploiting CVE-2025-55292 may cause minor changes to data without severely impacting its accuracy.
  • Availability: None
    CVE-2025-55292 does not impact system availability.

CVE-2025-55292 References

External References

CWE Common Weakness Enumeration

CWE-348

CAPEC Common Attack Pattern Enumeration and Classification

  • Cache Poisoning CAPEC-141 An attacker exploits the functionality of cache technologies to cause specific data to be cached that aids the attackers' objectives. This describes any attack whereby an attacker places incorrect or harmful material in cache. The targeted cache can be an application's cache (e.g. a web browser cache) or a public cache (e.g. a DNS or ARP cache). Until the cache is refreshed, most applications or clients will treat the corrupted cache value as valid. This can lead to a wide range of exploits including redirecting web browsers towards sites that install malware and repeatedly incorrect calculations based on the incorrect value.
  • DNS Cache Poisoning CAPEC-142 A domain name server translates a domain name (such as www.example.com) into an IP address that Internet hosts use to contact Internet resources. An adversary modifies a public DNS cache to cause certain names to resolve to incorrect addresses that the adversary specifies. The result is that client applications that rely upon the targeted cache for domain name resolution will be directed not to the actual address of the specified domain name but to some other address. Adversaries can use this to herd clients to sites that install malware on the victim's computer or to masquerade as part of a Pharming attack.
  • User-Controlled Filename CAPEC-73 An attack of this type involves an adversary inserting malicious characters (such as a XSS redirection) into a filename, directly or indirectly that is then used by the target software to generate HTML text or other potentially executable content. Many websites rely on user-generated content and dynamically build resources like files, filenames, and URL links directly from user supplied data. In this attack pattern, the attacker uploads code that can execute in the client browser and/or redirect the client browser to a site that the attacker owns. All XSS attack payload variants can be used to pass and exploit these vulnerabilities.
  • Manipulating Web Input to File System Calls CAPEC-76 An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.
  • AJAX Footprinting CAPEC-85 This attack utilizes the frequent client-server roundtrips in Ajax conversation to scan a system. While Ajax does not open up new vulnerabilities per se, it does optimize them from an attacker point of view. A common first step for an attacker is to footprint the target environment to understand what attacks will work. Since footprinting relies on enumeration, the conversational pattern of rapid, multiple requests and responses that are typical in Ajax applications enable an attacker to look for many vulnerabilities, well-known ports, network locations and so on. The knowledge gained through Ajax fingerprinting can be used to support other attacks, such as XSS.

Vulnerable Configurations

  • cpe:2.3:o:meshtastic:meshtastic_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.0.3:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.0.3:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.0.4:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.0.4:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.0.5:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.0.5:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.0.9:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.0.9:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.1.0:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.1.0:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.1.3:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.1.3:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.1.5:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.1.5:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.1.6:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.1.6:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.1.7:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.1.7:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.1.8:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.1.8:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.1.9:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.1.9:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.1.10:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.1.10:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.2.0:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.2.0:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.2.3:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.2.3:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.4.1:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.4.1:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.4.2:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.4.2:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.4.3:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.4.3:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.6.0:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.6.0:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.6.1:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.6.1:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.6.2:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.6.2:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.6.3:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.6.3:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.6.4:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.6.4:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.6.7:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.6.7:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.6.8:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.6.8:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.7.4:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.7.4:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.7.5:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.7.5:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.7.6:-:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.7.6:-:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.7.6:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.7.6:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.7.7:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.7.7:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.7.8:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.7.8:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.7.9:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.7.9:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.7.10:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.7.10:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.7.11:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.7.11:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.8.1:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.8.1:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.8.2:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.8.2:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.9.1:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.9.1:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.9.2:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.9.2:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.9.3:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.9.3:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.9.5:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.9.5:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.9.6:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.9.6:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:0.9.7:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:0.9.7:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.0.0:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.0.0:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.0:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.0:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.1:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.1:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.2:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.2:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.3:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.3:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.4:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.4:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.5:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.5:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.6:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.6:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.7:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.7:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.8:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.8:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.20:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.20:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.23:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.23:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.30:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.30:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.31:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.31:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.32:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.32:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.33:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.33:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.42:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.42:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.46:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.46:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.47:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.47:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.48:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.48:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.50:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.1.50:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.2.1:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.2.1:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.2.4:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.2.4:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.2.5:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.2.5:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.2.6:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.2.6:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.2.9:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.2.9:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.2.10:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.2.10:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.2.11:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.2.11:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.2.13:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.2.13:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.2.16:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.2.16:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.2.17:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.2.17:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.2.20:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.2.20:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.2.23:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.2.23:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.2.25:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.2.25:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:1.2.28:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:1.2.28:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:2.4.1:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:2.4.1:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:2.5.0:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:2.5.0:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:2.5.1:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:2.5.1:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:2.5.6:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:2.5.6:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:2.5.19:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:2.5.19:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:2.6.2:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:2.6.2:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:2.6.3:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:2.6.3:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:2.6.6:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:2.6.6:*:*:*:*:*:*:*
  • cpe:2.3:o:meshtastic:meshtastic_firmware:2.6.11:*:*:*:*:*:*:*
    cpe:2.3:o:meshtastic:meshtastic_firmware:2.6.11:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2025-55292: 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-29023 – Keygraph Shannon contains a hard-coded API key in its router configuration that, when the router component is enabled and exposed, allows network a...
  • CVE-2025-70039 – An issue pertaining to CWE-78: Improper Neutralization of Special Elements used in an OS Command was discovered in linagora Twake v2023.Q1.1223.
  • CVE-2025-70038 – An issue pertaining to CWE-79: Improper Neutralization of Input During Web Page Generation was discovered in linagora Twake v2023.Q1.1223. This all...
  • CVE-2025-70034 – An issue pertaining to CWE-1333: Inefficient Regular Expression Complexity (4.19) was discovered in mscdex ssh2 v1.17.0.
  • CVE-2025-70033 – An issue pertaining to CWE-79: Improper Neutralization of Input During Web Page Generation was discovered in Sunbird-Ed SunbirdEd-portal v1.13.4.