Home/CVE/Cursor is a code editor built for programming with AI. In versions prior to 3.0.0, the Cursor Desktop could execute work
CVE
CVE-2026-48124
Cursor is a code editor built for programming with AI. In versions prior to 3.0.0, the Cursor Desktop could execute work
Cursor is a code editor built for programming with AI. In versions prior to 3.0.0, the Cursor Desktop could execute workspace-defined Claude hook commands from .claude/settings.local.json without dedicated user approval. A malicious workspace or agent-created file could configure hooks that run local commands in the user's context when an agent turn ends.
This could allow sandbox escape, persistence across turns, local data access, or follow-on compromise. This issue has been fixed in version 3.0.0.
EPSS 0.00022
Monitor
- ⚠ NVD has not scored this CVE yet - manual triage required (common for recent CVEs)
Sigma rules0
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2026-48124, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
◆
ATT&CK techniques
11Techniques this CVE enables - linked via CWECAPECATT&CK. High◆ = named directly in ATT&CK or Nuclei templates.
T1027.006 · HTML Smuggling T1027.009 · Embedded Payloads T1055 · Process Injection T1176 · Software Extensions T1195.001 · Compromise Software Dependencies and Development Tools T1505.004 · IIS Components T1505.005 · Terminal Services DLL T1564.009 · Resource Forking T1574.006 · Dynamic Linker Hijacking T1574.013 · KernelCallbackTable T1620 · Reflective Code Loading
▤ Build a SIEM detection for these techniques
▤
CAPEC attack patterns
12Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.
CAPEC-CAPEC-175 · Code Inclusion CAPEC-CAPEC-201 · Serialized Data External Linking CAPEC-CAPEC-228 · DTD Injection CAPEC-CAPEC-242 · Code Injection CAPEC-CAPEC-251 · Local Code Inclusion CAPEC-CAPEC-252 · PHP Local File Inclusion CAPEC-CAPEC-253 · Remote Code Inclusion CAPEC-CAPEC-263 · Force Use of Corrupted Files CAPEC-CAPEC-35 · Leverage Executable Code in Non-Executable Files CAPEC-CAPEC-538 · Open-Source Library Manipulation CAPEC-CAPEC-549 · Local Execution of Code CAPEC-CAPEC-640 · Inclusion of Code in Existing Process
⬡
Weakness Classification
▣