How severe is CVE-2026-62431?

CVE-2026-62431 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.

Is CVE-2026-62431 being actively exploited?

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

How do I fix CVE-2026-62431?

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

When was CVE-2026-62431 published?

CVE-2026-62431 was published on 2026-07-28.

CVE-2026-62431

CVE-2026-62431 is a high-severity vulnerability with a CVSS 3.x base score of 7.5. 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-369.

Key facts

Severity: High (CVSS 3.x base score 7.5)
EPSS exploit prediction: 0% (31st percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-369
Published: 2026-07-28
Last modified: 2026-07-28

Description

The logic to handle periodic Viridian STIMERs performs a division with an unchecked user-controlled divisor value, that can be set to zero to cause a #DE fault.

Frequently asked questions

What is CVE-2026-62431?: The logic to handle periodic Viridian STIMERs performs a division with an unchecked user-controlled divisor value, that can be set to zero to cause a #DE fault.
How severe is CVE-2026-62431?: CVE-2026-62431 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2026-62431 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (31st percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-62431?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2026-62431 published?: CVE-2026-62431 was published on 2026-07-28.

References

Other CWE-369 (Divide By Zero) vulnerabilities

CVE-2021-32494 — Critical (CVSS 10.0): Radare2 has a division by zero vulnerability in Mach-O parser's rebase_buffer function. This allow attackers to create…
CVE-2024-57932 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: gve: guard XDP xmit NDO on existence of xdp…
CVE-2017-11720 — Critical (CVSS 9.8): There is a division-by-zero vulnerability in LAME 3.99.5, caused by a malformed input file.
CVE-2020-20892 — High (CVSS 8.8): An issue was discovered in function filter_frame in libavfilter/vf_lenscorrection.c in Ffmpeg 4.2.1, allows attackers…
CVE-2025-4637 — High (CVSS 8.7): Divide By Zero vulnerability in davisking dlib allows remote attackers to cause a denial of service via a crafted…
CVE-2026-37232 — High (CVSS 8.6): An issue was discovered in OpenAirInterface5G 2.4.0 (nr-softmodem) in the E2SM-KPM RAN Function's PRB utilization…

Browse all CWE-369 (Divide By Zero) vulnerabilities →