How severe is CVE-2026-42996?

CVE-2026-42996 has a CVSS 4.0 base score of 10.0, rated critical severity.

Is CVE-2026-42996 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (38th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-42996?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

Does CVE-2026-42996 have an EU (EUVD) identifier?

Yes. CVE-2026-42996 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-26482.

When was CVE-2026-42996 published?

CVE-2026-42996 was published on 2026-05-01 and last updated on 2026-06-17.

CVE-2026-42996

CVE-2026-42996 is a critical-severity vulnerability with a CVSS 4.0 base score of 10.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-121.

Key facts

Severity: Critical (CVSS 4.0 base score 10.0)
EPSS exploit prediction: 0% (38th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-26482
Weakness: CWE-121
Published: 2026-05-01
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2026-42996?: 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.
How severe is CVE-2026-42996?: CVE-2026-42996 has a CVSS 4.0 base score of 10.0, rated critical severity.
Is CVE-2026-42996 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (38th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-42996?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2026-42996 have an EU (EUVD) identifier?: Yes. CVE-2026-42996 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-26482.
When was CVE-2026-42996 published?: CVE-2026-42996 was published on 2026-05-01 and last updated on 2026-06-17.

References

Other CWE-121 (Stack-based Buffer Overflow) vulnerabilities

CVE-2026-12848 — Critical (CVSS 10.0): GV-I/O Box 4E is a smart embedded device with 4 input and 4 relays output that can be controlled over Ethernet and…
CVE-2026-12847 — Critical (CVSS 10.0): GV-I/O Box 4E is a smart embedded device with 4 input and 4 relays output that can be controlled over Ethernet and…
CVE-2026-12846 — Critical (CVSS 10.0): GV-I/O Box 4E is a smart embedded device with 4 input and 4 relays output that can be controlled over Ethernet and…
CVE-2026-12485 — Critical (CVSS 10.0): GV-I/O Box 4E is a smart embedded device with 4 input and 4 relays output that can be controlled over Ethernet and…
CVE-2026-37541 — Critical (CVSS 10.0): Buffer overflow vulnerability in Open Vehicle Monitoring System 3 (OVMS3) 3.3.005. In canformat_gvret.cpp, the length…
CVE-2017-20230 — Critical (CVSS 10.0): Storable versions before 3.05 for Perl has a stack overflow. The retrieve_hook function stored the length of the class…

Browse all CWE-121 (Stack-based Buffer Overflow) vulnerabilities →