CVE-2025-24797
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMeshtastic 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceBuffer overflow vulnerability in Meshtastic's mesh packet handling when processing malformed protobuf data. Attackers can send specially crafted packets containing invalid protobuf to overflow a buffer, hijack execution flow, and achieve remote code execution. No authentication or user interaction required if the target device rebroadcasts packets on the default channel.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.6.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed firmware versionConnect to the Meshtastic device via the mobile app, CLI (meshtastic --info), or serial interface and retrieve the current firmware version numberAffected if The firmware version is below 2.6.2 (e.g., 2.5.x, 2.4.x, or earlier)
-
Verify default channel configurationInspect the device channel settings to determine if the default "LongFast" channel (or any unsecured default channel) is active and in useAffected if The default channel with default PSK is enabled, allowing automatic packet rebroadcasting
-
Confirm packet rebroadcasting is enabledCheck the device settings for nodeinfo rebroadcasting and packet routing options (typically enabled by default)Affected if Packet rebroadcasting is turned on, which allows attacker packets to reach the device and be processed
-
Assess radio range exposureDetermine if the device is operating in an environment where untrusted or unknown mesh nodes could be within radio rangeAffected if The device is in an area where unknown attackers could transmit malicious protobuf payloads within radio range
A device is affected if it is running Meshtastic firmware version below 2.6.2, has the default channel active with rebroadcasting enabled, and is within radio range of potentially untrusted mesh nodes.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.6.2
Upgrade Meshtastic firmware/software to version 2.6.2 or later. Until patched, consider disabling automatic packet rebroadcasting on default channels or implementing network segmentation to limit exposure.
Meshtastic Firmware 2.6.2
- Obtain Meshtastic Firmware version 2.6.2 or later from the official Meshtastic GitHub releases or firmware distribution channels
- Flash the updated firmware (2.6.2 or later) to the affected Meshtastic device using the standard firmware flashing process
- Verify the device is running the updated firmware version after flashing
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24797 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-24797 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data