JetBrains YouTrack authorization bypass in app widgets
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.2.19840
- Who is exposed
- Not reported
Summary
In JetBrains YouTrack before 2026.2.19840 app widgets could perform API requests on behalf of viewing users without their consent
What to do
Upgrade to a fixed version: 2026.2.19840.
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-133258 (In JetBrains YouTrack before 2026.2.19840 app widgets could perform API requests on behalf of viewing users without their consent), 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-133258 (entry last updated 2026-11-19):
Affected:
- JetBrains YouTrack: fixed in 2026.2.19840
Fixed versions: 2026.2.19840.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133258 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133258 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-133258
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-133258"}.Affected versions
- JetBrains YouTrackfixed in 2026.2.19840
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity4.8/10CVSS 4.8
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 27 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-133258 |
| Record | NVD · CVE-2026-133258 |
Questions about CVE-2026-133258
Is CVE-2026-133258 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-133258?
YouTrack: before 2026.2.19840.
Source: cve.now feed data
How do I fix CVE-2026-133258?
Upgrade to a fixed version: 2026.2.19840.
Source: cve.now feed data
Related
- CVE-2026-133256In JetBrains YouTrack before 2026.2.19840 improper authorization allowed project administrators to obtain GitLab tokens of other projects
- CVE-2026-133260In JetBrains YouTrack before 2026.2.19840 privilege escalation from project administrator to system administrator was possible via group…
- CVE-2026-133262In JetBrains YouTrack before 2026.2.19766 improper authorization allowed read-only users to change the visibility of restricted issues via…
- CVE-2026-133261In JetBrains YouTrack before 2026.2.19840 an HTML injection in email notifications was possible via issue descriptions
- CVE-2026-133257In JetBrains YouTrack before 2026.2.19840 improper authorization allowed read-only users to modify and delete articles
- CVE-2026-123331In JetBrains YouTrack before 2026.2.19197 article editors could change visibility of restricted child articles
No corrections so far. Something wrong on this page? Report an error.