CVE-2026-49367
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 · uneditedIn JetBrains IntelliJ IDEA before 2026.1.1 command execution was possible via the guest user account
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 confidenceA vulnerability in JetBrains IntelliJ IDEA versions prior to 2026.1.1 allows command execution through the guest user account. This appears to be an authentication/authorization bypass where the guest account, which may be enabled by default or easily accessible, permits execution of arbitrary commands on the host system, potentially leading to full system compromise.
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< 2026.1.1CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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.
-
Determine installed IntelliJ IDEA versionOpen IntelliJ IDEA and go to Help > About, or check the installation directory for version information. Alternatively, check your system's installed programs list.Affected if version is earlier than 2026.1.1
-
Identify if guest user account functionality is configuredCheck IntelliJ IDEA settings under Settings > Appearance & Behavior > System Settings > Guest User Accounts, or search for guest user related configuration files in the IDE config directory.Affected if guest user accounts are enabled or have been used in the IDE
-
Review IDE execution framework policiesInspect the IDE's built-in terminal, run configurations, and any script execution settings under Settings > Build, Execution, Deployment > Terminal or similar execution-related panels.Affected if arbitrary command execution features are accessible to guest or authenticated users without proper isolation
You are affected if your IntelliJ IDEA version is below 2026.1.1 and guest user accounts are or were enabled in the IDE, allowing potential command execution by authenticated users.
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 · scoped2026.1.1
Upgrade to IntelliJ IDEA 2026.1.1 or later. If immediate upgrade is not feasible, disable the guest user account in the IDE settings and ensure proper authentication is enforced for all IDE features and remote capabilities.
IntelliJ IDEA 2026.1.1
- Back up your IntelliJ IDEA configuration, projects, and any custom settings
- Download IntelliJ IDEA 2026.1.1 or later from the official JetBrains website (www.jetbrains.com)
- Install the new version 2026.1.1 over your existing installation, or to a new directory
- Launch IntelliJ IDEA 2026.1.1 and verify the guest user account no longer has command execution capabilities
- Migrate any necessary custom settings or plugins from your previous installation if needed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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 $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49367 — 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-49367 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