CVE-2026-56770

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM 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.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 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(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
45%
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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
python-libais0.17+git.20190917.master.e464cf8-2, 0.17+git.20190917.master.e464cf8-3, 0.17+git.20190917.master.e464cf8-4, 0.17+git.20190917.master.e464cf8-5, 0.17+git.20190917.master.e464cf8-6——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
python-libais0.17+git.20190917.master.e464cf8-3, 0.17+git.20190917.master.e464cf8-4, 0.17+git.20190917.master.e464cf8-5, 0.17+git.20190917.master.e464cf8-6——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
python-libais0.17+git.20190917.master.e464cf8-5, 0.17+git.20190917.master.e464cf8-6——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
python-libais0.17+git.20190917.master.e464cf8-5, 0.17+git.20190917.master.e464cf8-6——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 106× 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.

Showing the most recent 100 of 206 total refreshes for this CVE.

  1. 2026-08-27 14:25 UTCEPSS rescore
  2. 2026-08-26 14:46 UTCEPSS rescore
  3. 2026-08-25 13:49 UTCEPSS rescore
  4. 2026-08-25 00:53 UTCEG score recompute
  5. 2026-08-25 00:53 UTCGHSA enrichment
  6. 2026-08-24 13:09 UTCEG score recompute
  7. 2026-08-24 13:09 UTCGHSA enrichment
  8. 2026-08-23 21:49 UTCGHSA enrichment
  9. 2026-08-23 10:05 UTCEG score recompute
  10. 2026-08-23 10:05 UTCGHSA enrichment
  11. 2026-08-23 00:19 UTCEPSS rescore
  12. 2026-08-22 22:22 UTCGHSA enrichment
  13. 2026-08-22 10:01 UTCEG score recompute
  14. 2026-08-22 10:01 UTCGHSA enrichment
  15. 2026-08-21 23:49 UTCEPSS rescore
  16. 2026-08-21 18:12 UTCGHSA enrichment
  17. 2026-08-21 06:29 UTCEG score recompute
  18. 2026-08-21 06:29 UTCGHSA enrichment
  19. 2026-08-20 22:55 UTCEPSS rescore
  20. 2026-08-20 18:45 UTCGHSA enrichment
  21. 2026-08-20 07:02 UTCEG score recompute
  22. 2026-08-20 07:02 UTCGHSA enrichment
  23. 2026-08-19 17:04 UTCEPSS rescore
  24. 2026-08-19 13:05 UTCGHSA enrichment
  25. 2026-08-19 01:14 UTCEG score recompute
Show 75 more
  1. 2026-08-19 01:14 UTCGHSA enrichment
  2. 2026-08-18 13:48 UTCEPSS rescore
  3. 2026-08-17 13:47 UTCEPSS rescore
  4. 2026-08-17 10:25 UTCGHSA enrichment
  5. 2026-08-16 22:42 UTCEG score recompute
  6. 2026-08-16 22:42 UTCGHSA enrichment
  7. 2026-08-16 14:56 UTCEPSS rescore
  8. 2026-08-16 10:59 UTCEG score recompute
  9. 2026-08-16 10:59 UTCGHSA enrichment
  10. 2026-08-16 02:14 UTCEPSS rescore
  11. 2026-08-15 23:16 UTCGHSA enrichment
  12. 2026-08-15 11:32 UTCEG score recompute
  13. 2026-08-15 11:32 UTCGHSA enrichment
  14. 2026-08-15 01:30 UTCEPSS rescore
  15. 2026-08-14 23:48 UTCGHSA enrichment
  16. 2026-08-14 12:05 UTCGHSA enrichment
  17. 2026-08-14 00:22 UTCEG score recompute
  18. 2026-08-14 00:22 UTCGHSA enrichment
  19. 2026-08-13 22:00 UTCEPSS rescore
  20. 2026-08-13 12:38 UTCGHSA enrichment
  21. 2026-08-13 00:53 UTCEG score recompute
  22. 2026-08-13 00:53 UTCGHSA enrichment
  23. 2026-08-12 13:51 UTCEPSS rescore
  24. 2026-08-12 13:10 UTCGHSA enrichment
  25. 2026-08-12 01:26 UTCEG score recompute
  26. 2026-08-12 01:26 UTCGHSA enrichment
  27. 2026-08-11 13:43 UTCGHSA enrichment
  28. 2026-08-11 01:59 UTCEG score recompute
  29. 2026-08-11 01:59 UTCGHSA enrichment
  30. 2026-08-11 00:00 UTCEPSS rescore
  31. 2026-08-10 14:16 UTCGHSA enrichment
  32. 2026-08-10 02:32 UTCGHSA enrichment
  33. 2026-08-09 14:49 UTCEG score recompute
  34. 2026-08-09 14:49 UTCGHSA enrichment
  35. 2026-08-09 13:46 UTCEPSS rescore
  36. 2026-08-09 03:06 UTCEG score recompute
  37. 2026-08-09 03:06 UTCGHSA enrichment
  38. 2026-08-08 16:37 UTCEPSS rescore
  39. 2026-08-08 15:23 UTCGHSA enrichment
  40. 2026-08-08 03:40 UTCEG score recompute
  41. 2026-08-08 03:40 UTCGHSA enrichment
  42. 2026-08-07 15:56 UTCGHSA enrichment
  43. 2026-08-07 04:13 UTCGHSA enrichment
  44. 2026-08-06 16:29 UTCEG score recompute
  45. 2026-08-06 16:29 UTCGHSA enrichment
  46. 2026-08-06 13:47 UTCEPSS rescore
  47. 2026-08-06 04:46 UTCEG score recompute
  48. 2026-08-06 04:46 UTCGHSA enrichment
  49. 2026-08-05 19:17 UTCEPSS rescore
  50. 2026-08-05 17:03 UTCGHSA enrichment
  51. 2026-08-05 02:47 UTCEG score recompute
  52. 2026-08-05 02:47 UTCGHSA enrichment
  53. 2026-08-04 15:10 UTCEPSS rescore
  54. 2026-08-04 15:03 UTCEG score recompute
  55. 2026-08-04 15:03 UTCGHSA enrichment
  56. 2026-08-04 10:39 UTCEPSS rescore
  57. 2026-08-04 01:41 UTCGHSA enrichment
  58. 2026-08-03 13:57 UTCEG score recompute
  59. 2026-08-03 13:57 UTCGHSA enrichment
  60. 2026-08-03 10:36 UTCEPSS rescore
  61. 2026-08-03 01:35 UTCGHSA enrichment
  62. 2026-08-02 13:52 UTCEG score recompute
  63. 2026-08-02 13:52 UTCGHSA enrichment
  64. 2026-08-02 02:27 UTCEPSS rescore
  65. 2026-08-02 02:08 UTCGHSA enrichment
  66. 2026-08-01 14:24 UTCEG score recompute
  67. 2026-08-01 14:24 UTCGHSA enrichment
  68. 2026-08-01 04:16 UTCEPSS rescore
  69. 2026-08-01 02:40 UTCGHSA enrichment
  70. 2026-07-31 14:43 UTCGHSA enrichment
  71. 2026-07-31 02:55 UTCEG score recompute
  72. 2026-07-31 02:55 UTCGHSA enrichment
  73. 2026-07-30 16:28 UTCEPSS rescore
  74. 2026-07-30 14:02 UTCEG score recompute
  75. 2026-07-30 14:02 UTCGHSA enrichment

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 1% probability of exploitation in the next 30 days, which ranks it in the top 54.7% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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