Cursor Agent Segfaults on Launch?

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

I cannot launch agent or cursor-agent, I’ve updated my IDE as usual as far as I remember.

$ cursor-agent --version
2025.09.18-7ae6800
$ cursor-agent upgrade
Checking for updates...
zsh: segmentation fault  cursor-agent upgrade
$ curl https://cursor.com/install -fsS | bash
....
✨ Installation Complete! 
Start using Cursor Agent:
   agent
Happy coding! 🚀
$ agent
zsh: segmentation fault  agent
$ agent --version
2026.01.28-fd13201

Steps to Reproduce

Presumably download those two tools from those two dates on MacOS. Other AIs claim ‘The crash is in X509_get_subject_name during certificate loading.’ and say this:

│ Cause │ Bug in Node.js v24’s --use-system-ca handling of macOS Keychain certificates
│ Crash location │ X509_get_subject_name called with null X509 pointer
│ Trigger │ Likely a malformed or unusual certificate in your 554 Keychain certs
│ Fix applied │ Added export NODE_OPTIONS=“–use-openssl-ca” to ~/.zshrc

Expected Behavior

It should run.

Operating System

MacOS

Version Information

$ agent about
About Cursor CLI

CLI Version         2026.01.28-fd13201
Model               Auto
OS                  darwin (arm64)
Terminal            warp
Shell               zsh
User Email          Not logged in

Cursor IDE about:

Version: 2.4.27
VSCode Version: 1.105.1
Commit: 4f2b772756b8f609e1354b3063de282ccbe7a690
Date: 2026-01-31T21:24:58.143Z
Build Type: Stable
Release Track: Early Access
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 23.6.0

For AI issues: which model did you use?

N/A

For AI issues: add Request ID with privacy disabled

N/A

Does this stop you from using Cursor

Yes - Cursor CLI is unusable

3

After I added export NODE_OPTIONS=“–use-openssl-ca” to ~/.zshrc, now I do agent login and even though the browser seems to pass, the terminal says Signing in with the browser…✗ Login failedLogin failed or timed out.

This fix in ~/.local/share/cursor-agent/versions/2026.01.28-fd13201/cursor-agent seems to fix it:

  22 +# Workaround for Node.js v24 crash when reading macOS Keychain certificates with --use-system-ca                                          
  23 +# Export system root certificates to avoid the buggy Keychain reading code                                                                
  24 +CA_BUNDLE="$HOME/.config/cursor-agent/ca-bundle.pem"
  25 +if [ ! -f "$CA_BUNDLE" ]; then                                                                                                            
  26 +  mkdir -p "$(dirname "$CA_BUNDLE")"                                                                                                      
  27 +  security find-certificate -a -p /System/Library/Keychains/SystemRootCertificates.keychain > "$CA_BUNDLE" 2>/dev/null || true            
  28 +fi                                                                                                                                        
  29 +export NODE_EXTRA_CA_CERTS="$CA_BUNDLE"                                                                                                   
  30 +                                                                                                                                          
  31 +exec -a "$0" "$NODE_BIN" "$SCRIPT_DIR/index.js" "$@" ```
4

Hey @yush_g!

Thanks for reporting. If you’d be willing to reproduce it and grab the crash report (~/Library/Logs/DiagnosticReports/), we can look into it some more! Otherwise, thanks for sharing your workaround.

5

Hmm those logs seem to be gone now unfortunately. I suspect it may have to do with agent symlinking to the old cursor-agent binary that I reinstalled.

1 Like