CVE-2024-28960VulnerabilityPublished 29 Mar 2024Updated 4 Nov 2025

CVE-2024-28960: mbedtls · n/a

Affects mbedtlsSource CVE Database V5

Not known to be exploited · CVSS 8.2 High : upgrade to 3.6.0 or 2.28.8 soon.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

8.2High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.6.0, 2.28.8

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Mar 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade mbed-tls/mbedtls to 3.6.0 or 2.28.8.

Affected software

Product	Affected	Fixed in
GitHubmbed-tls/mbedtls`pkg:github/mbed-tls/mbedtls`Other threats	Affected =2.18.0 >=2.18.0 <2.28.8 >=3.0.0 <3.6.0	Fixed in 2.28.8 3.6.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should take immediate steps to mitigate CVE-2024-28960 by upgrading affected Mbed TLS versions to 2.28.8 or later and Mbed Crypto to 3.6.0 or later once patches are officially released. If you cannot patch yet, organizations should audit their use of the PSA Crypto API to identify and restrict any shared memory operations that could be exploited. Employ network segmentation and strict access controls to limit exposure of vulnerable devices to untrusted networks. Implement monitoring for unusual cryptographic API usage patterns or memory access anomalies that could indicate exploitation attempts. For embedded device manufacturers, incorporate secure coding practices to avoid shared memory mishandling and conduct thorough security testing of cryptographic components. Additionally, coordinate with supply chain partners to ensure that firmware and software updates addressing this vulnerability are deployed promptly. Finally, maintain up-to-date inventories of devices using Mbed TLS or Mbed Crypto to prioritize remediation efforts effectively.

Description

An issue was discovered in Mbed TLS 2.18.0 through 2.28.x before 2.28.8 and 3.x before 3.6.0, and Mbed Crypto. The PSA Crypto API mishandles shared memory.

Impact

For European organizations, the impact of CVE-2024-28960 is significant, especially for those deploying embedded systems, IoT devices, or industrial control systems that utilize Mbed TLS or Mbed Crypto for cryptographic operations. Confidentiality breaches could lead to exposure of sensitive data, including cryptographic keys, which may facilitate further attacks such as data decryption, impersonation, or unauthorized access to protected resources. Critical infrastructure sectors such as energy, manufacturing, and telecommunications, which increasingly rely on embedded cryptography, are at heightened risk. The vulnerability's remote exploitability without authentication or user interaction increases the attack surface, potentially allowing attackers to compromise devices at scale. This could disrupt supply chains, cause data breaches, or undermine trust in secure communications. Given the widespread use of Mbed TLS in embedded and IoT devices, the scope of affected systems is broad, encompassing devices deployed in both enterprise and operational technology environments across Europe.

CWE-284Improper Access Control (opens in a new tab)
Pillar weaknessCWE Top 25 (2025): #19OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Operation
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
Attack patterns
Embedding Scripts within Scripts (opens in a new tab)
Modification of Windows Service Configuration (opens in a new tab)
Malicious Root Certificate (opens in a new tab)
Intent Spoof (opens in a new tab)
WebView Exposure (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Nov 2025, 18:29 UTC

WeaknessesCWE-284

Technical details

References

Community reviews

Related threats