CVE-2026-31854
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCursor is a code editor built for programming with AI. Prior to 2.0 ,if a visited website contains maliciously crafted instructions, the model may attempt to follow them in order to “assist” the user. When combined with a bypass of the command whitelist mechanism, such indirect prompt injections could result in commands being executed automatically, without the user’s explicit intent, thereby posing a significant security risk. This vulnerability is fixed in 2.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is an indirect prompt injection vulnerability in Cursor (AI code editor) where malicious instructions embedded in visited websites could be interpreted by the AI model. When combined with a bypass of the command whitelist mechanism, this allowed unauthorized commands to be executed automatically without explicit user consent, representing a significant security risk.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Cursor versionOpen Cursor and navigate to Help > About, or check the application package details. Compare the version number against 2.0. Any version below 2.0 is affected.Affected if The installed version is below 2.0
-
Verify command whitelist configurationExamine Cursor's configuration files for any custom command whitelist settings. Look in the user's config directory (typically ~/.cursor or similar) for settings related to allowed commands or AI command execution permissions.Affected if Custom or weakened whitelist configurations exist that allow commands not explicitly approved
-
Review AI chat/command execution logsCheck Cursor's logs and any AI interaction history for commands that executed without visible user approval. Look for automated command executions that do not correspond to explicit user actions.Affected if Commands appear in logs or history that were not explicitly authorized by the user
-
Inspect network connections to untrusted domainsReview Cursor's network activity or browser component for connections to malicious websites that could have delivered indirect prompt injections. Check any proxy or network logs for suspicious referrers.Affected if Cursor has connected to untrusted or malicious websites that could have injected hostile prompts
A user is affected if their Cursor version is below 2.0 and the AI model has executed commands that bypassed the whitelist, potentially without explicit user consent.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.0
Upgrade to Cursor version 2.0 or later which contains the fix for this vulnerability.
Cursor 2.0 or later
- Check current Cursor version by opening Cursor and navigating to Help > About Cursor
- Back up any necessary Cursor settings, extensions, or workspace configurations if desired
- Download the latest Cursor 2.0 or later version from the official cursor.sh website or GitHub releases
- Install the new version by running the downloaded installer
- Restart Cursor after installation completes
- Verify the installation by checking Help > About Cursor shows version 2.0 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-31854 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-31854 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data