CVE-2026-56770

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-39523 (ENISA EUVD) · GHSA-2f4m-q55c-v3xr (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

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

The CVE record's CNA (VulnCheck) lists schwehr libais versions up to and including 0.15 as affected. No release containing a fix is confirmed on record.

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.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.6%
EPSS %ILE
47th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 25, 2026

Last Modified

October 25, 2026

Advisory Details (2)

Auto-updated Jun 25, 2026
No fix on record yet.
Web page

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
Web page

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 rangeFix by version rangeDependents
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
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
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
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-libais0.17+git.20190917.master.e464cf8-5, 0.17+git.20190917.master.e464cf8-6
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
python-libais0.17+git.20190917.master.e464cf8-5, 0.17+git.20190917.master.e464cf8-6
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 43× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 285 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 185 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-56770?
CVE-2026-56770 is a high-severity vulnerability; its CVE record was 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 made public?
CVE-2026-56770 was made public on June 24, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on June 25, 2026. EchelonGraph's copy of the record carries a last-modified date of October 25, 2026; the record at its source may have been updated since.
Is CVE-2026-56770 actively exploited?
CVE-2026-56770 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56770?
CVE-2026-56770 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-56770?
No fix for CVE-2026-56770 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (VulnCheck) lists schwehr libais versions up to and including 0.15 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-56770 are linked in the Vendor Advisories panel on this page.

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.