Cursor 15.4.1 on macOS Configuration default permission

Summaryinfo

A vulnerability, which was classified as critical, has been found in Cursor 15.4.1 on macOS. This issue affects some unknown processing of the component Configuration Handler. The manipulation leads to default permission. This vulnerability is listed as CVE-2025-9190. The attack must be carried out locally. There is no available exploit.

Detailsinfo

A vulnerability was found in Cursor 15.4.1 on macOS and classified as critical. This issue affects an unknown functionality of the component Configuration Handler. The manipulation with an unknown input leads to a default permission vulnerability. Using CWE to declare the problem leads to CWE-276. During installation, installed file permissions are set to allow anyone to modify those files. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

The configuration of Cursor on macOS, specifically the "RunAsNode" fuse enabled, allows a local attacker with unprivileged access to execute arbitrary code that inherits Cursor TCC (Transparency, Consent, and Control) permissions. Acquired resource access is limited to previously granted permissions by the user. Accessing other resources beyond previously granted TCC permissions will prompt the user for approval in the name of Cursor, potentially disguising attacker's malicious intent. This issue was detected in 15.4.1 version of Cursor. Project maintainers decided not to fix this issue, because a scenario including a local attacker falls outside their defined threat model.

The weakness was presented with Karol Mazurek as GHSA-xp8w-f7f4-r544. The advisory is shared at afine.com. The identification of this vulnerability is CVE-2025-9190 since 08/19/2025. The exploitation is known to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1222 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Cursor

Version

• 15.4.1

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion