Cyber Resilience

CVE-2025-41724

Published
22 October 2025
Modified
15 April 2026
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0044 37th percentile
Risk Priority 57 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-41724 is a high-severity Failure to Handle Incomplete Element (CWE-239) vulnerability in Certvde (inferred from references). Its CVSS base score is 7.5 (High).

Operationally, ranked at the 37th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

An unauthenticated remote attacker can crash the wscserver by sending incomplete SOAP requests. The wscserver process will not be restarted by a watchdog and a device reboot is necessary to make it work again.

CWE(s)
CWE-239

Related Threats

CVEs Like This One

CVE-2024-29155Shared CWE-239

Affected Assets

Certvde
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

Input validation directly enforces completeness checks on supplied elements before they are accepted for processing.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require robust input validation and error handling for incomplete or malformed elements.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect incomplete-element handling but does not itself prevent the weakness in production code.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle requires input validation and completeness checks that reduce incomplete-element handling failures.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate handling of incomplete or malformed inputs, mitigating this weakness.

A.8.28 Secure coding partial match
prevents

Secure coding standards typically include rules for validating element completeness, directly addressing CWE-239.

References