dbcve.org
Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2026-42467

HIGH · 7.5 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 →
84/100
Remediation priority · High
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
An issue was discovered in Open-SAE-J1939 thru commit b6caf884df46435e539b1ecbf92b6c29b345bdfe (2025-11-30) in SAE_J1939_Read_Binary_Data_Transfer_DM16 causing a denial of service via crafted CAN frame on the J1939 bus.

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

A denial of service vulnerability exists in Open-SAE-J1939's SAE_J1939_Read_Binary_Data_Transfer_DM16 function through commit b6caf884df46435e539b1ecbf92b6c29b345bdfe. The function fails to properly validate or bounds-check incoming CAN frame data during binary data transfer (DM16) processing, allowing an attacker on the J1939 bus to trigger a crash or hang by sending a specially crafted CAN frame.

MitigationImplement robust input validation and bounds checking in the SAE_J1939_Read_Binary_Data_Transfer_DM16 function to verify CAN frame payload lengths and values before processing. Consider adding defensive error handling to gracefully manage malformed frames without causing a denial of service.

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/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 checks

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

  1. Identify Open-SAE-J1939 usage
    Search your codebase, build artifacts, or embedded system for files or libraries originating from the Open-SAE-J1939 project. Look for source files named j1939*.c or j1939*.h, or linked library objects containing 'sae_j1939' in their name.
    Affected if Open-SAE-J1939 is present in the system
  2. Determine the version or commit
    If using git, run 'git log --oneline' in the Open-SAE-J1939 repository directory and check if commit b6caf884df46435e539b1ecbf92b6c29b345bdfe or any commit prior to it is included in your build. If using a release, compare the release version to the timeline of commits around b6caf884df.
    Affected if The installed version includes commit b6caf884df or an earlier commit
  3. Verify SAE_J1939_Read_Binary_Data_Transfer_DM16 function exists
    Search the source code for the function 'SAE_J1939_Read_Binary_Data_Transfer_DM16'. Use grep or similar: grep -r 'SAE_J1939_Read_Binary_Data_Transfer_DM16' .
    Affected if The function is present in the codebase
  4. Check if DM16 binary data transfer is enabled
    Search for calls to the DM16 function or references to binary data transfer in your application code. Look for usage patterns like 'SAE_J1939_Read_Binary_Data_Transfer_DM16' being invoked, or configuration enabling DM16/PGN 0xEA00 (the PGN for DM16).
    Affected if DM16 binary data transfer functionality is actively used or configured in the application
  5. Confirm CAN frame reception is exposed
    Determine whether the J1939 stack processes incoming CAN frames from external sources. Review the main loop or interrupt handlers that call the J1939 reception functions (such as SAE_J1939_Receive) and verify if the CAN interface can receive frames from untrusted bus participants.
    Affected if The system accepts and processes incoming CAN frames from the J1939 bus

You are affected if your environment uses Open-SAE-J1939 at a version that includes commit b6caf884df or earlier, the SAE_J1939_Read_Binary_Data_Transfer_DM16 function exists, DM16 binary data transfer is enabled, and the system processes incoming CAN frames from the bus.

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

Implement robust input validation and bounds checking in the SAE_J1939_Read_Binary_Data_Transfer_DM16 function to verify CAN frame payload lengths and values before processing. Consider adding defensive error handling to gracefully manage malformed frames without causing a denial of service.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42467 — 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-42467 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