How severe is CVE-2025-15497?

CVE-2025-15497 has a CVSS 4.0 base score of 3.8, rated low severity.

Is CVE-2025-15497 being actively exploited?

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

How do I fix CVE-2025-15497?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2025-15497 have an EU (EUVD) identifier?

Yes. CVE-2025-15497 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-206570.

When was CVE-2025-15497 published?

CVE-2025-15497 was published on 2026-01-30 and last updated on 2026-06-17.

CVE-2025-15497

CVE-2025-15497 is a low-severity vulnerability with a CVSS 4.0 base score of 3.8. 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: Low (CVSS 4.0 base score 3.8)
EPSS exploit prediction: 0% (24th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-206570
Weakness: CWE-617
Published: 2026-01-30
Last modified: 2026-06-17

Description

Insufficient epoch key slot processing in OpenVPN 2.7_alpha1 through 2.7_rc5 allows remote authenticated users to trigger an assert resulting in a denial of service

Frequently asked questions

What is CVE-2025-15497?: Insufficient epoch key slot processing in OpenVPN 2.7_alpha1 through 2.7_rc5 allows remote authenticated users to trigger an assert resulting in a denial of service
How severe is CVE-2025-15497?: CVE-2025-15497 has a CVSS 4.0 base score of 3.8, rated low severity.
Is CVE-2025-15497 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (24th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-15497?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-15497 have an EU (EUVD) identifier?: Yes. CVE-2025-15497 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-206570.
When was CVE-2025-15497 published?: CVE-2025-15497 was published on 2026-01-30 and last updated on 2026-06-17.

References

Other CWE-617 (Reachable Assertion) vulnerabilities

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-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…
CVE-2020-6623 — High (CVSS 8.8): stb stb_truetype.h through 1.22 has an assertion failure in stbtt__cff_get_index.
CVE-2020-6619 — High (CVSS 8.8): stb stb_truetype.h through 1.22 has an assertion failure in stbtt__buf_seek.

Browse all CWE-617 (Reachable Assertion) vulnerabilities →