JetBrains ReSharper server impersonation in What's New feature
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.3
- Who is exposed
- Not reported
Summary
In JetBrains ReSharper, the What's New feature did not verify server certificates. An attacker positioned on the network can exploit this remotely, without logging in, to impersonate the server and potentially read or alter some information.
Written by a model
Original description
In JetBrains ReSharper before 2026.3 the What's New feature did not verify server certificates
What to do
Upgrade to a fixed version: 2026.3.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133180 (In JetBrains ReSharper before 2026.3 the What's New feature did not verify server certificates), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133180 (entry last updated 2026-11-19):
Affected:
- JetBrains ReSharper: fixed in 2026.3
Fixed versions: 2026.3.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133180 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133180 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.jetbrains.com/privacy-security/issues-fixed/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133180
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133180"}.Affected versions
- JetBrains ReSharperfixed in 2026.3
cve.now Index
- Exploitation0/40No signal
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity3.7/10CVSS 3.7
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 26 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | jetbrains.com · privacy-security/issues-fixed |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133180 |
| Record | NVD · CVE-2026-133180 |
Questions about CVE-2026-133180
Is CVE-2026-133180 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-133180?
ReSharper: before 2026.3.
Source: cve.now feed data
How do I fix CVE-2026-133180?
Upgrade to a fixed version: 2026.3.
Source: cve.now feed data
Related
- CVE-2025-64456In JetBrains ReSharper before 2025.2.4 missing signature verification in DPA Collector allows local privilege escalation
- CVE-2025-23385In JetBrains ReSharper before 2024.3.4, 2024.2.8, and 2024.1.7, Rider before 2024.3.4, 2024.2.8, and 2024.1.7, dotTrace before 2024.3.4, 202
- CVE-2025-64457In JetBrains ReSharper, Rider and dotTrace before 2025.2.5 local privilege escalation was possible via race condition
- CVE-2026-133181In JetBrains ReSharper before 2026.3 server host names were not verified during certificate validation
- CVE-2026-133254In JetBrains IntelliJ IDEA before 2026.3, 2026.2.4 code execution was possible in untrusted projects via the Code Provenance plugin
- CVE-2026-133253In JetBrains IntelliJ IDEA before 2026.3 untrusted projects could read files of other open projects via the built-in web server
No corrections so far. Something wrong on this page? Report an error.