CVE-2022-46826
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 2022.3 the built-in web server allowed an arbitrary file to be read by exploiting a path traversal vulnerability.
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 confidenceThe built-in web server in JetBrains IntelliJ IDEA before version 2022.3 contained a path traversal vulnerability that allowed remote attackers to read arbitrary files on the host system by manipulating file paths in HTTP requests to the web server.
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< 2022.3CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 IntelliJ IDEA versionOpen IntelliJ IDEA, go to Help > About (or IntelliJ IDEA > About on macOS) to view the installed version number. Compare it to the affected range of versions before 2022.3.Affected if The installed version is any version prior to 2022.3 (for example, 2022.2, 2022.1, 2021.x, or earlier).
-
Verify built-in web server was usedLook for indicators that the built-in web server feature was activated. Check recent project logs, run configurations, or temporary files that may contain web server activity records. The feature is typically accessible via Run > Debug configurations or by running an application that starts an internal web server.Affected if The built-in web server feature was used or configured in the IDE, making it reachable for HTTP requests.
-
Review IDE network exposureCheck if the IDE or the built-in web server was accessible over the network rather than only on localhost. Examine network configuration settings, firewall rules, or proxy settings that may have allowed external access to the IDE's web server ports.Affected if The built-in web server was exposed to network access beyond localhost, allowing remote attackers to send malicious HTTP requests.
A user is affected if they used a version of IntelliJ IDEA prior to 2022.3 with the built-in web server feature enabled and exposed to network requests.
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 · scoped2022.3
Upgrade IntelliJ IDEA to version 2022.3 or later to obtain the patched version. If immediate upgrade is not possible, disable the built-in web server feature or restrict network access to the IDE.
2022.3
- Back up your IntelliJ IDEA settings and project configurations
- Download IntelliJ IDEA version 2022.3 or later from the official JetBrains website (www.jetbrains.com)
- Close any running instances of IntelliJ IDEA
- Install the downloaded version, or use the IDE's built-in update mechanism to check for updates and install 2022.3+
- Restart IntelliJ IDEA after the update completes
- Verify the installation by checking Help > About to confirm the version is 2022.3 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46826 — 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-2022-46826 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