dbcve.org
Stack-based Buffer OverflowWeakness · CWE-121

CVE-2026-37539

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Buffer overflow vulnerability in cannelloni v2.0.0 in CAN frame parsing in parser.cpp in function parseCANFrame, and decoder.cpp in function decodeFrame allowing remote attackers to cause a denial of service (crash) or possibly execute arbitrary code via crafted CAN FD 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 confidence

Buffer overflow in cannelloni v2.0.0 during CAN FD frame parsing in parser.cpp (parseCANFrame) and decoder.cpp (decodeFrame) functions allows attackers to cause denial of service or potentially execute arbitrary code via crafted CAN FD frames with malformed length or payload data that exceeds buffer bounds.

MitigationUpdate to patched version if available; otherwise implement strict bounds checking and input validation on CAN FD frame lengths and payloads in parseCANFrame and decodeFrame functions before buffer operations.

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify cannelloni installation and version
    Run 'cannelloni -v' or 'cannelloni --version', or check package manager: 'dpkg -l | grep cannelloni' (Debian) or 'rpm -qi cannelloni' (RHEL)
    Affected if Version is exactly v2.0.0 or falls within the v2.0.0 release line (no patched version indicated)
  2. Confirm CAN FD frame parsing is enabled
    Inspect cannelloni configuration files (typically in /etc/cannelloni/ or /etc/cannelloni.d/) for CAN FD-related settings such as 'enable_canfd', 'fd_mode', or 'canfd' flags in interface configuration sections
    Affected if CAN FD support is explicitly enabled in the configuration or default settings apply FD frame handling
  3. Verify CAN FD interface is active
    Run 'ip link show' or 'ifconfig' to list network interfaces, then check if any CAN FD interfaces (typically named can0, can1, vcan0 with FD mode) are in UP state; also check running cannelloni process: 'ps aux | grep cannelloni' and review its active interfaces
    Affected if A CAN FD interface is configured and active with cannelloni consuming frames from it
  4. Check for external CAN FD frame sources
    Review cannelloni logs (journalctl -u cannelloni or /var/log/cannelloni.log) for incoming CAN FD frame connections from untrusted sources; examine network binding configuration: 'netstat -tlnp | grep cannelloni' to see exposed endpoints
    Affected if Cannelloni is receiving CAN FD frames from network sources that could send crafted malformed frames
  5. Review parseCANFrame and decodeFrame usage
    If source code inspection is possible, verify that the binary links against the affected parser.cpp/decoder.cpp from v2.0.0; use 'strings <cannelloni_binary> | grep -i parseCANFrame' or 'ldd <cannelloni_binary>' to confirm library versions in use
    Affected if Binary is built from v2.0.0 source and processes CAN FD frames through the vulnerable functions

You are affected if cannelloni v2.0.0 is running with CAN FD frame parsing enabled and accepting CAN FD frames from any source, since malformed FD frames can trigger the buffer overflow in parseCANFrame or decodeFrame.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to patched version if available; otherwise implement strict bounds checking and input validation on CAN FD frame lengths and payloads in parseCANFrame and decodeFrame functions before buffer operations.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-37539 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-37539 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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