VulnerabilityPublished 17 Sep 2024Updated 4 Nov 2025

CVE-2024-40847: The issue was addressed with additional code-signing restrictions

Source GCVE Database

Compare

Authoritative record:CVE-2024-40847· Medium 5.5

Not known to be exploited · CVSS 5.5 Medium.

Data as of 4 Nov 2026, 17:17 UTC

CVSS 3.1 base score

5.5Medium

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

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

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

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: None: There is no loss of integrity within 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 16 Sep 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 4 Nov 2026.

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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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.

ghsa-gw53-chv8-4wr2

What to do

AI-suggested

Apply the official fixes by updating to macOS Ventura 13.7, macOS Sonoma 14.7, or macOS Sequoia 15, where the issue is resolved by additional code-signing restrictions. No other mitigation steps are indicated.

Description

CVE-2024-40847 is a vulnerability in macOS where an application may be able to access sensitive user data due to insufficient code-signing restrictions. The issue is addressed by additional code-signing restrictions implemented in macOS Ventura 13.7, macOS Sonoma 14.7, and macOS Sequoia 15. The vulnerability has a medium severity with a CVSS score of 5.5.

Impact

An application with local access and low privileges may exploit this vulnerability to access sensitive user data, potentially compromising user privacy. The integrity and availability of the system are not affected. The medium severity reflects the limited attack vector and privileges required.

Summary

This vulnerability (CVE-2024-40847) involves an app potentially accessing sensitive user data on macOS due to inadequate code-signing restrictions. Apple has fixed this issue by enhancing code-signing requirements in macOS Ventura 13.7, Sonoma 14.7, and Sequoia 15. The CVSS 3.1 vector indicates the attack requires local access with low complexity and low privileges, no user interaction, and impacts confidentiality but not integrity or availability.

References

Community reviews

Loading reviews…