CVE-2025-9190

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 attackers 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.

Weakness

During installation, installed file permissions are set to allow anyone to modify those files.

Potential Mitigations

• 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.
• Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

Related Attack Patterns

• https://cwe.mitre.org/data/definitions/1.html
• https://cwe.mitre.org/data/definitions/127.html
• https://cwe.mitre.org/data/definitions/81.html

References

• https://afine.com/threat-of-tcc-bypasses-on-macos/#cooking-cursor-app
• https://cert.pl/posts/2025/08/tcc-bypass/
• https://github.com/cursor/cursor
• https://github.com/cursor/cursor/security/advisories/GHSA-xp8w-f7f4-r544