CVE-2026-29974
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 was discovered in kosma minmea 0.3.0. The minmea_scan functions format specifier copies NMEA field data to a caller-provided buffer without a size parameter. Applications using minmea_scan on untrusted input are vulnerable to a stack buffer overflow.
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 minmea_scan function in minmea library 0.3.0 copies NMEA field data to a caller-provided buffer using format specifiers but lacks a size parameter, allowing an attacker to overflow the stack buffer when processing untrusted NMEA input data.
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 checksWork through these to decide whether this CVE applies to you.
-
Locate minmea library in the environmentSearch for minmea source files (minmea.h, minmea.c) or linked library binaries. Check project dependencies for 'minmea' package reference.Affected if minmea library source code or binary is present in the codebase or runtime environment
-
Verify minmea library versionInspect the version defined in minmea.h (look for #define MINMEA_VERSION or similar), check package manager version if installed as dependency, or examine library binary metadata.Affected if version is 0.3.0 or falls within the 0.3.x branch without patched bounds checking
-
Identify usage of minmea_scan functionSearch source code for calls to minmea_scan() function. Review function signatures in minmea.h to confirm the function accepts a buffer parameter without size limit.Affected if codebase contains calls to minmea_scan that pass a buffer without accompanying size parameter
-
Confirm stack buffer usage with minmea_scanExamine how minmea_scan is called - look for stack-allocated char buffers passed as destination (e.g., char buf[64]; minmea_scan(..., buf, ...)). Check if buffer size is hardcoded without bounds checking.Affected if stack-allocated fixed-size buffers are passed to minmea_scan without size validation
-
Assess NMEA input source trust levelTrace data flow to minmea_scan: identify if NMEA data originates from untrusted sources such as network sockets, serial/UART ports, user-uploaded files, or external APIs.Affected if NMEA input comes from untrusted external sources without prior length validation
Environment is affected if minmea library version 0.3.0 is in use, minmea_scan is called with stack buffers, and untrusted NMEA data flows into the vulnerable function without length checks.
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 dataImplement bounds checking by adding size parameters to buffer operations, replace unsafe string functions with bounded alternatives (e.g., snprintf), and validate NMEA input length before processing.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-29974 — 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-29974 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