CVE-2026-54413
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 · unediteddriftregion iso14229 through 0.9.0 contains an integer underflow and downstream out-of-bounds read in the Handle_0x27_SecurityAccess function in iso14229.c that allows a remote unauthenticated attacker to crash a UDS server and potentially read memory past the receive buffer by sending a single-byte 0x27 SecurityAccess request that follows any earlier well-formed 0x27 message.
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 confidenceThe iso14229 library through 0.9.0 has an integer underflow in Handle_0x27_SecurityAccess() where a single-byte 0x27 request causes recv_len - UDS_0X27_REQ_BASE_LEN to underflow to 65535, which is then used as a length parameter to SecAccessValidateKey/SecAccessRequestSeed callbacks, resulting in out-of-bounds memory reads past the 4-KB receive buffer.
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
- Low
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 iso14229 library versionLocate the iso14229 library in your project (check package.json, requirements.txt, vendor directory, or compiled binary) and determine its version number. Compare against the affected range: versions up to and including 0.9.0 are vulnerable.Affected if The library version is 0.9.0 or lower.
-
Verify UDS Security Access (0x27) handler is in useCheck if your application implements or uses the UDS Security Access service (service ID 0x27). Review your iso14229 configuration, look for Handle_0x27_SecurityAccess calls, or examine the UDS service handlers registered in your diagnostic stack.Affected if The UDS Security Access (0x27) handler from iso14229 is actively used or exposed.
-
Confirm recv_len validation is absentInspect the source code of Handle_0x27_SecurityAccess() in your iso14229 library. Look for a bounds check that ensures recv_len >= 2 before accessing recv_buf[1] and performing the subtraction (recv_len - UDS_0X27_REQ_BASE_LEN).Affected if No such validation exists; the code accesses recv_buf[1] and performs the subtraction without first verifying recv_len >= 2.
-
Check for memory boundary exposureIf you cannot inspect source code, test the UDS server with a Security Access request packet containing exactly 1 byte (just the service ID 0x27 with no additional data). Observe whether the server crashes, hangs, or exhibits abnormal memory behavior.Affected if Sending a 1-byte Security Access request triggers a crash, excessive memory read, or unexpected server behavior.
You are affected if your environment uses iso14229 library version 0.9.0 or earlier AND the UDS Security Access (0x27) handler is enabled, with no recv_len >= 2 validation present in the code path.
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 dataAdd a recv_len lower-bound check (recv_len >= 2) before indexing recv_buf[1] in Handle_0x27_SecurityAccess(), matching the pattern used by all other UDS sub-function handlers in the library.
- Consultation1.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-54413 — 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-54413 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