CVE-2026-31280
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 · uneditedAn issue in the Bluetooth RFCOMM service of Parani M10 Motorcycle Intercom v2.1.3 allows unauthorized attackers to cause a Denial of Service (DoS) via supplying crafted RFCOMM frames.
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 · moderate confidenceA Denial of Service vulnerability exists in the Bluetooth RFCOMM service of Parani M10 Motorcycle Intercom v2.1.3. Attackers can send specially crafted RFCOMM frames to trigger the DoS condition, causing the device's Bluetooth functionality to become unresponsive or crash.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Identify the device modelLocate the physical Parani M10 intercom unit or check product documentation/packaging. Confirm the device is a Parani M10 Motorcycle Intercom.Affected if The device is NOT a Parani M10 - if it is a different model, this specific CVE does not apply.
-
Check the firmware versionAccess the Parani M10 firmware settings through the device menu, companion mobile app, or check the product label/ documentation. Locate the firmware version number.Affected if The firmware version is 2.1.3 or lower (e.g., 2.1.2, 2.1.1, 2.1.0, etc.). Versions prior to the fix are affected.
-
Confirm Bluetooth RFCOMM availabilityVerify that Bluetooth functionality is enabled on the Parani M10. As an intercom device, RFCOMM is typically active by default for device pairing and communication.Affected if Bluetooth is enabled and the device is in discoverable/pairing mode - the RFCOMM service is active and reachable.
-
Assess Bluetooth exposureDetermine whether the device is paired with untrusted devices or remains discoverable in public/high-risk areas where attackers could send malicious RFCOMM frames.Affected if The device Bluetooth is active and accessible to untrusted or unknown devices within range.
You are affected if you own a Parani M10 Motorcycle Intercom running firmware version 2.1.3 or lower with Bluetooth functionality enabled.
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.
From vendor dataContact Parani for firmware updates addressing this vulnerability. If no update is available, reduce attack surface by disabling Bluetooth when not in use and avoiding pairing with untrusted devices.
- Consultation2.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-31280 — 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-2026-31280 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