dbcve.org
Intellij IdeaApplication · Jetbrains

CVE-2026-49382

HIGH · 7.8 CVSS v3.1 Published 2026-05-29
Fix available
A fix is available. Upgrade to 2026.1 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
In JetBrains IntelliJ IDEA before 2026.1 code execution was possible via template injection in the Copyright plugin

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 · high confidence

Template injection vulnerability in the Copyright plugin of JetBrains IntelliJ IDEA versions prior to 2026.1 allows authenticated attackers to execute arbitrary code through malicious template inputs.

MitigationUpgrade IntelliJ IDEA to version 2026.1 or later to obtain the patched Copyright plugin.

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
Intellij IdeaApplication
Affected:< 2026.1

CVSS 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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check IntelliJ IDEA version
    Go to Help > About (or IntelliJ IDEA > About on macOS) to view the installed version number
    Affected if The version displayed is any build prior to 2026.1 (for example, 2025.3, 2025.2, etc.)
  2. Verify Copyright plugin presence
    Open Settings > Plugins > Installed and search for 'Copyright' in the plugin list
    Affected if The Copyright plugin is installed and enabled (it comes bundled with IDEA)
  3. Check for custom copyright templates
    Go to Settings > Editor > Copyright > Copyright Profiles and examine any configured copyright profiles
    Affected if A custom copyright profile is configured - this indicates the vulnerable feature is in use

You are affected if you are running any IntelliJ IDEA version earlier than 2026.1 and have the Copyright plugin enabled with custom templates configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2026.1 or later
Fixed in 2026.1
Interim mitigation

Upgrade IntelliJ IDEA to version 2026.1 or later to obtain the patched Copyright plugin.

Recommended fix High confidence

2026.1

  1. Open IntelliJ IDEA
  2. Navigate to Help > Check for Updates (or IntelliJ IDEA > Check for Updates on macOS)
  3. If an update to version 2026.1 or later is available, download and install it
  4. Restart IntelliJ IDEA to complete the installation
  5. Alternatively, download IntelliJ IDEA 2026.1 directly from www.jetbrains.com/idea/download/ and reinstall
Caveat Minor IDE upgrades typically have minimal breaking changes; verify plugin compatibility with 2026.1 if using third-party plugins

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Intellij Idea Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-49382 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-49382 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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