CVE-2026-42996

CRITICALNVD 10.010.0
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit probability: 0.6% (47th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-26482 (ENISA EUVD) · GHSA-j23g-7p7w-3f6j (GitHub Security Advisories)Source: ENISA EUVD

10.0EG
EchelonGraph verdictPlan a fixRemediate 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: 10.0Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

JS8Call through 2.3.1 and JS8Call-improved before 3.0 have a stack-based buffer overflow via a radio transmission of @APRSIS GRID followed by a long Maidenhead locator. This occurs in grid2deg in APRSISClient.cpp.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
76
EG Risk 76/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)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 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, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
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 (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 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, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 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 total (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

May 1, 2026

Last Modified

October 26, 2026

Advisory Details (4)

Auto-updated Oct 26, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Stack overflow processing APRS GRID · Advisory · JS8Call-improved/JS8Call-improved · GitHub

https://github.com/JS8Call-improved/JS8Call-improved/security/advisories/GHSA-98hp-pjp7-w62x
Web page

js8call/APRSISClient.cpp at fd721e8b67eed84cb3c09d018205ab9a53e1a8b1 · js8call/js8call · GitHub

https://github.com/js8call/js8call/blob/fd721e8b67eed84cb3c09d018205ab9a53e1a8b1/APRSISClient.cpp#L89-L102
GitHub commit Patch Available

commit a6c7a19b82bb (JS8Call-improved/JS8Call-improved)

Patch available: JS8Call-improved/JS8Call-improved v3.0.1 (contains commit a6c7a19b82bb)

https://github.com/JS8Call-improved/JS8Call-improved/commit/a6c7a19b82bbd7c2c0c892576f84d7449e8c7088

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 69× 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 341 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 241 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-42996?
CVE-2026-42996 is a critical-severity vulnerability; its CVE record was published on May 1, 2026. JS8Call through 2.3.1 and JS8Call-improved before 3.0 have a stack-based buffer overflow via a radio transmission of @APRSIS GRID followed by a long Maidenhead locator. This occurs in grid2deg in APRSISClient.cpp.
When was the CVE record for CVE-2026-42996 published?
The CVE record for CVE-2026-42996 was published on May 1, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 26, 2026; the record at its source may have been updated since.
Is CVE-2026-42996 actively exploited?
CVE-2026-42996 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-42996?
CVE-2026-42996 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2026-42996?
A fix for CVE-2026-42996 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-42996?

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