CVE-2026-86506: In JetBrains GoLand before 2026.2.2.1 missing authentication on the GoLand profiler's injected pprof server exposed profiling data
Noroxi assessment
Priority: Monitor (action score 23/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.37% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: JetBrains GoLand 2026.2.2.1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to JetBrains GoLand 2026.2.2.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
- Published
- Sep 7, 2026
- Updated
- Sep 8, 2026
- EPSS
- 0.3% · 32th percentile
- CWE
- CWE-306
Report tools
Action score
23
Low priority for now.
- CVSS
- 23 / 40 · 5.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · JetBrains
- 5.9
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (JetBrains). Independent of NVD's CPE analysis and usually ahead of it.
JetBrains GoLand
- before 2026.2.2.1affected · semver
Same product
jetbrains: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-53915In JetBrains GoLand before 2026.1.3 remote code execution was possible via untrusted project configuration35Monitor
- CVE-2026-64803In JetBrains GoLand before 2026.2 arbitrary code execution was possible before granting project trust via the configured Go SDK31Monitor
- CVE-2026-64802In JetBrains GoLand before 2026.2 arbitrary code execution was possible before granting project trust in the Go Modules integration31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2020-11685Apr 22, 2020 · In JetBrains GoLand before 2019.3.2, the plugin repository was accessed via HTTP instead of HTTPS.30Monitor
- ← EarlierCVE-2025-29932Mar 25, 2025 · In JetBrains GoLand before 2025.1 an XXE during debugging was possible21Monitor
- ← EarlierCVE-2026-64800Jul 23, 2026 · In JetBrains GoLand before 2026.2 sensitive configuration values written to log files by default22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| JetBrains GoLand | 2026.2.2.1 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1031 · Sep 8, 2026(JetBrains Çoklu Ürün Güvenlik Bildirimi)
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-306 · Missing Authentication for Critical FunctionCVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-secondary
Root cause
A function added for development or support ships to production without authentication. It often relies on the assumption that it is “only reachable from the internal network.”
The bug in code
The whole CWE-306 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
// Added for the support team
app.post("/maintenance/reset", resetDevice);Fixed
if (config.maintenanceEnabled) {
app.post(
"/maintenance/reset",
requireSession, requireRole("admin"), resetDevice
);
}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.