How severe is CVE-2026-39453?

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

Is CVE-2026-39453 being actively exploited?

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

How do I fix CVE-2026-39453?

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-39453 published?

CVE-2026-39453 was published on 2026-10-09 and last updated on 2026-10-11.

CVE-2026-39453

CVE-2026-39453 is a high-severity vulnerability with a CVSS 3.x base score of 8.3. 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-617.

Key facts

Severity: High (CVSS 3.x base score 8.3)
CVSS v4: 8.5
EPSS exploit prediction: 0% (20th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-617
Published: 2026-10-09
Last modified: 2026-10-11

Description

Navigating to a certain URL on the switch’s web server causes the switch to reboot. This can be automated using a tool like curl to create DoS conditions where the switch constantly reboots.

Frequently asked questions

What is CVE-2026-39453?: Navigating to a certain URL on the switch’s web server causes the switch to reboot. This can be automated using a tool like curl to create DoS conditions where the switch constantly reboots.
How severe is CVE-2026-39453?: CVE-2026-39453 has a CVSS 3.x base score of 8.3, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity high, and availability high.
Is CVE-2026-39453 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (20th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-39453?: 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-39453 published?: CVE-2026-39453 was published on 2026-10-09 and last updated on 2026-10-11.

References

Other CWE-617 (Reachable Assertion) vulnerabilities

CVE-2024-35884 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: udp: do not accept non-tunnel GSO skbs landing in…
CVE-2020-3615 — Critical (CVSS 9.8): Valid deauth/disassoc frames is dropped in case if RMF is enabled and some rouge peer keep on sending rogue…
CVE-2019-9795 — Critical (CVSS 9.8): A vulnerability where type-confusion in the IonMonkey just-in-time (JIT) compiler could potentially be used by…
CVE-2026-52952 — High (CVSS 8.8): In the Linux kernel, the following vulnerability has been resolved: iommu: Fix WARN_ON in…
CVE-2026-31739 — High (CVSS 8.8): In the Linux kernel, the following vulnerability has been resolved: crypto: tegra - Add missing CRYPTO_ALG_ASYNC The…
CVE-2020-12417 — High (CVSS 8.8): Due to confusion about ValueTags on JavaScript Objects, an object may pass through the type barrier, resulting in…

Browse all CWE-617 (Reachable Assertion) vulnerabilities →