CVE-2026-56770

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
7.5(high)
EPSS
25.9%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 25, 2026

Advisory Details (2)

Auto-updated Jun 25, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic

libais 0.15 - Out-of-bounds Vector Access in VdmStream::AddLine via Invalid Sequential Message ID | Advisories | VulnCheck

https://www.vulncheck.com/advisories/libais-out-of-bounds-vector-access-in-vdmstream-addline-via-invalid-sequential-message-id
generic🟡 PoC Available

Out-of-Bounds `std::vector` Index in libais `VdmStream::AddLine` via Attacker-Controlled AIS Sequence ID · Issue #263 · schwehr/libais · GitHub

https://github.com/schwehr/libais/issues/263

Vendor Advisories for CVE-2026-56770(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 38× in last 7d / 61× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 18:13 UTCEG score recompute
  2. 2026-07-06 18:12 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 06:11 UTCEG score recompute
  6. 2026-07-06 06:11 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 18:17 UTCEG score recompute
  10. 2026-07-05 18:16 UTCGHSA enrichment
  11. 2026-07-05 06:32 UTCEG score recompute
  12. 2026-07-05 06:31 UTCGHSA enrichment
  13. 2026-07-05 02:31 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-04 18:48 UTCEG score recompute
  16. 2026-07-04 18:48 UTCGHSA enrichment
  17. 2026-07-04 07:00 UTCEG score recompute
  18. 2026-07-04 06:59 UTCGHSA enrichment
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-03 18:56 UTCEG score recompute
  22. 2026-07-03 18:56 UTCGHSA enrichment
  23. 2026-07-03 07:11 UTCEG score recompute
  24. 2026-07-03 07:11 UTCGHSA enrichment
  25. 2026-07-02 19:27 UTCEG score recompute
Show 36 more
  1. 2026-07-02 19:27 UTCGHSA enrichment
  2. 2026-07-02 07:43 UTCEG score recompute
  3. 2026-07-02 07:43 UTCGHSA enrichment
  4. 2026-07-01 20:00 UTCEG score recompute
  5. 2026-07-01 20:00 UTCGHSA enrichment
  6. 2026-07-01 15:07 UTCEPSS rescore
  7. 2026-07-01 08:16 UTCEG score recompute
  8. 2026-07-01 08:16 UTCGHSA enrichment
  9. 2026-06-30 23:22 UTCEPSS rescore
  10. 2026-06-30 20:32 UTCEG score recompute
  11. 2026-06-30 20:32 UTCGHSA enrichment
  12. 2026-06-30 08:48 UTCEG score recompute
  13. 2026-06-30 08:48 UTCGHSA enrichment
  14. 2026-06-29 21:05 UTCEG score recompute
  15. 2026-06-29 21:05 UTCGHSA enrichment
  16. 2026-06-29 14:06 UTCEPSS rescore
  17. 2026-06-29 09:22 UTCEG score recompute
  18. 2026-06-29 09:22 UTCGHSA enrichment
  19. 2026-06-28 21:39 UTCEG score recompute
  20. 2026-06-28 21:39 UTCGHSA enrichment
  21. 2026-06-28 14:07 UTCEPSS rescore
  22. 2026-06-28 09:56 UTCEG score recompute
  23. 2026-06-28 09:55 UTCGHSA enrichment
  24. 2026-06-28 04:56 UTCEPSS rescore
  25. 2026-06-28 04:56 UTCEPSS rescore
  26. 2026-06-27 22:12 UTCEG score recompute
  27. 2026-06-27 22:12 UTCGHSA enrichment
  28. 2026-06-27 10:27 UTCEG score recompute
  29. 2026-06-27 10:27 UTCGHSA enrichment
  30. 2026-06-27 03:08 UTCEPSS rescore
  31. 2026-06-26 22:43 UTCEG score recompute
  32. 2026-06-26 22:43 UTCGHSA enrichment
  33. 2026-06-26 10:57 UTCEG score recompute
  34. 2026-06-26 10:57 UTCGHSA enrichment
  35. 2026-06-25 19:49 UTCEG score recompute
  36. 2026-06-25 19:49 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-56770?
CVE-2026-56770 is a high vulnerability published on June 25, 2026. 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,…
When was CVE-2026-56770 disclosed?
CVE-2026-56770 was first published in the National Vulnerability Database on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56770 actively exploited?
CVE-2026-56770 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 25.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56770?
CVE-2026-56770 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-56770?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56770, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-56770

Explore →

Is Your Infrastructure Affected by CVE-2026-56770?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs