Cyber Resilience

CVE-2024-58249

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

Summary

CVE-2024-58249 is a low-severity Premature Release of Resource During Expected Lifetime (CWE-826) vulnerability. Its CVSS base score is 3.7 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 40th 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 SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

In wxWidgets before 3.2.7, a crash can be triggered in wxWidgets apps when connections are refused in wxWebRequestCURL.

CWE(s)
CWE-826

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-24912Shared CWE-826
CVE-2023-1297Shared CWE-826
CVE-2024-51727Shared CWE-826
CVE-2026-31663Shared CWE-826
CVE-2026-45984Shared CWE-826
CVE-2026-53322Shared CWE-826
CVE-2026-32748Shared CWE-826
CVE-2026-33526Shared CWE-826
CVE-2025-31115Shared CWE-826

Affected Assets

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover premature-release defects before deployment.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles can require correct resource lifetime management so the premature-release pattern is never coded.

SC-39 Process Isolation partial match

Process isolation confines the blast radius when a resource is released while still referenced inside another domain.

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 development practices directly address coding errors that release resources while they are still needed.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover instances of premature resource release after code is deployed.

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 premature-release bugs, providing partial mitigation.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle practices can include resource-lifetime checks that reduce premature-release defects.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate explicit resource-release rules, partially addressing the weakness.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles encourage proper resource scoping and lifetime management.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly prohibit premature resource release, covering most of the weakness.

A.8.32 Change management none match
none

Change-management processes may catch resource-handling regressions but do not directly prevent the weakness.

References