How severe is CVE-2025-24797?

CVE-2025-24797 has a CVSS 3.x base score of 9.4, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity low, and availability high.

Is CVE-2025-24797 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (56th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-24797?

CVE-2025-24797 affects Meshtastic Meshtastic Firmware. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2025-24797?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

Does CVE-2025-24797 have an EU (EUVD) identifier?

Yes. CVE-2025-24797 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-14855.

When was CVE-2025-24797 published?

CVE-2025-24797 was published on 2025-04-15 and last updated on 2026-06-17.

CVE-2025-24797

CVE-2025-24797 is a critical-severity vulnerability in Meshtastic Meshtastic Firmware with a CVSS 3.x base score of 9.4. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-119.

Key facts

Severity: Critical (CVSS 3.x base score 9.4)
EPSS exploit prediction: 1% (56th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-14855
Weakness: CWE-119
Affected product: Meshtastic Meshtastic Firmware
Published: 2025-04-15
Last modified: 2026-06-17

Description

Meshtastic is an open source mesh networking solution. A fault in the handling of mesh packets containing invalid protobuf data can result in an attacker-controlled buffer overflow, allowing an attacker to hijack execution flow, potentially resulting in remote code execution. This attack does not require authentication or user interaction, as long as the target device rebroadcasts packets on the default channel. This vulnerability fixed in 2.6.2.

Frequently asked questions

What is CVE-2025-24797?: Meshtastic is an open source mesh networking solution. A fault in the handling of mesh packets containing invalid protobuf data can result in an attacker-controlled buffer overflow, allowing an attacker to hijack execution flow, potentially resulting in remote code execution. This attack does not require authentication or user interaction, as long as the target device rebroadcasts packets on the default channel. This vulnerability fixed in 2.6.2.
How severe is CVE-2025-24797?: CVE-2025-24797 has a CVSS 3.x base score of 9.4, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity low, and availability high.
Is CVE-2025-24797 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (56th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-24797?: CVE-2025-24797 affects Meshtastic Meshtastic Firmware. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-24797?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2025-24797 have an EU (EUVD) identifier?: Yes. CVE-2025-24797 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-14855.
When was CVE-2025-24797 published?: CVE-2025-24797 was published on 2025-04-15 and last updated on 2026-06-17.

References

https://github.com/meshtastic/firmware/security/advisories/GHSA-33hw-xhfh-944r

Affected products (1)

cpe:2.3:o:meshtastic:meshtastic_firmware:*:*:*:*:*:*:*:*

More vulnerabilities in Meshtastic Meshtastic Firmware

CVE-2025-55293 — Critical (CVSS 9.4): Meshtastic is an open source mesh networking solution. Prior to v2.6.3, an attacker can send NodeInfo with a empty…
CVE-2025-52464 — High (CVSS 8.3): Meshtastic is an open source mesh networking solution. In versions from 2.5.0 to before 2.6.11, the flashing procedure…
CVE-2025-55292 — High (CVSS 8.2): Meshtastic is an open source mesh networking solution. In the current Meshtastic architecture, a Node is identified by…
CVE-2024-47078 — High (CVSS 8.1): Meshtastic is an open source, off-grid, decentralized, mesh network. Meshtastic uses MQTT to communicate over an…
CVE-2026-42566 — High (CVSS 7.5): Meshtastic is an open source mesh networking solution. Prior to version 2.7.23.b246bcd, a single node advertising a…
CVE-2024-45038 — High (CVSS 7.5): Meshtastic device firmware is a firmware for meshtastic devices to run an open source, off-grid, decentralized, mesh…

All CVEs affecting Meshtastic Meshtastic Firmware →

Other CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) vulnerabilities

CVE-2026-77946 — Critical (CVSS 10.0): A vulnerability was determined in TRENDnet TEW-821DAP 2.2.01b05. Affected by this vulnerability is the function…
CVE-2026-76008 — Critical (CVSS 10.0): A flaw has been found in Comfast CF-N1-S 2.6.0.1. This affects the function get_para_from_uri of the file…
CVE-2026-75784 — Critical (CVSS 10.0): A vulnerability was detected in TRENDnet TEW-WLC100 1v2.07b01. Affected by this issue is the function FUN_0040da4c of…
CVE-2026-74843 — Critical (CVSS 10.0): A vulnerability was determined in Wavlink WN531P3 and WN535M1 V250922. Affected by this vulnerability is the function…
CVE-2026-16367 — Critical (CVSS 10.0): Sandbox escape due to invalid pointer in the Disability Access APIs component. This vulnerability was fixed in Firefox…
CVE-2026-2778 — Critical (CVSS 10.0): Sandbox escape due to incorrect boundary conditions in the DOM: Core & HTML component. This vulnerability was fixed in…

Browse all CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) vulnerabilities →