dbcve.org
CWE-129Weakness · CWE-129

CVE-2026-56770

HIGH · 7.5 CVSS v3.1 Published 2026-06-25
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
libais through 0.15 VdmStream::AddLine uses an unchecked sentinel value as a vector index when processing AIS sentences with empty or out-of-range sequential message IDs. Remote attackers can crash services or vessel systems by sending crafted AIVDM sentences over VHF marine radio or IP feeds, causing out-of-bounds memory access and potential corruption.

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

libais through version 0.15 contains an out-of-bounds write vulnerability in the VdmStream::AddLine function, which uses an unchecked sentinel value derived from AIS sequential message IDs as a vector index. When processing crafted AIVDM sentences with empty or out-of-range message IDs, this allows attackers to trigger out-of-bounds memory access, causing service crashes or memory corruption in marine vessel systems.

MitigationUpdate libais to a patched version if available; otherwise, implement input validation to ensure sequential message IDs fall within valid vector bounds before indexing, and filter malformed AIS messages at network ingress.

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 if libais library is present
    Search for libais shared objects (libais.so, libais.a) in standard library paths (/usr/lib, /usr/local/lib, /opt) or check package manager (dpkg -l | grep libais, rpm -qa | grep libais)
    Affected if libais library is found on the system
  2. Determine installed libais version
    Run pkg-config --modversion libais, check library file version (ldd or file command), or query package manager; compare against affected range (all versions through 0.15)
    Affected if Installed version is 0.15 or any earlier version (0.x where x <= 15)
  3. Locate applications or services using libais
    Search for binaries that link to libais (ldd output on binaries, or grep for libais in /proc/<pid>/maps for running processes); identify AIS-related applications (aisdecoder, ais-tools, or custom marine software)
    Affected if An application using libais is running or installed to process AIS/AIVDM data
  4. Verify if AIVDM message processing is enabled
    Inspect application configuration for AIS input sources (AIVDM TCP/UDP listeners, file-based input, NMEA streams); check if VdmStream::AddLine code path is reachable by examining application logs or debugging
    Affected if The application is configured to parse incoming AIVDM sentences from network or untrusted sources
  5. Check for input validation on AIS message IDs
    Review application logs for crashes related to VdmStream, or test by sending crafted AIVDM messages with empty/out-of-range message ID fields (e.g., fragment sequences with missing or 0/255 ID values)
    Affected if The application accepts and processes AIVDM messages without validating sequential message IDs before vector indexing

The system is affected if libais version 0.15 or earlier is installed AND an application uses it to process AIVDM messages from external or untrusted sources without validating message ID bounds.

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 libais to a patched version if available; otherwise, implement input validation to ensure sequential message IDs fall within valid vector bounds before indexing, and filter malformed AIS messages at network ingress.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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