VulnerabilityPublished 9 Feb 2026

CVE-2026-25846: JetBrains YouTrack · Sensitive Data in Logs

Affects JetBrains YouTrackSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 2025.3.119033 when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.9% chance of exploitation in 30 days – higher than 62% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2025.3.119033

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade JetBrains YouTrack to 2025.3.119033.

Affected software

Product	Affected	Fixed in
JetBrainsYouTrack	Affected <2025.3.119033	Fixed in 2025.3.119033

AI-suggested

European organizations should immediately upgrade JetBrains YouTrack to version 2025.3.119033 or later, where this vulnerability is addressed. Until patching is complete, organizations should audit mailbox logs to identify and remove any exposed access tokens and restrict access to these logs to only trusted administrators. Implement strict access controls and monitoring on systems storing or processing YouTrack logs to detect unauthorized access attempts. Consider rotating access tokens that may have been exposed to invalidate compromised credentials. Additionally, review and enhance logging configurations to exclude sensitive information such as tokens from logs or use secure logging mechanisms that encrypt sensitive data. Network segmentation can limit attacker access to mailbox logs, reducing exploitation risk. Finally, educate development and operations teams on secure handling of authentication tokens and the importance of minimizing sensitive data exposure in logs.

Description

CVE-2026-25846 is a medium severity vulnerability in JetBrains YouTrack prior to version 2025.3.119033 where access tokens could be exposed in mailbox logs. This exposure stems from improper handling of sensitive information (CWE-532), potentially allowing attackers with network access and low privileges to obtain tokens without user interaction. While the vulnerability does not impact integrity or availability, the confidentiality breach could enable unauthorized access to YouTrack resources. No known exploits are currently reported in the wild. European organizations using affected YouTrack versions should prioritize updating to the patched release to prevent token leakage. Mitigation involves upgrading YouTrack, auditing mailbox logs for token exposure, and restricting log access. Countries with significant JetBrains YouTrack adoption, such as Germany, France, and the UK, are most likely to be impacted due to their large software development sectors. The vulnerability’s CVSS score of 6.

Impact

For European organizations, the exposure of access tokens in YouTrack mailbox logs can lead to unauthorized access to project management and issue tracking data, potentially compromising sensitive project information, intellectual property, and internal workflows. While the vulnerability does not directly affect system integrity or availability, the confidentiality breach can facilitate lateral movement within networks or unauthorized API usage, increasing the risk of further compromise. Organizations with extensive software development operations relying on YouTrack are particularly at risk, as attackers could leverage stolen tokens to manipulate issue tracking data or access confidential project details. The impact is heightened in regulated industries such as finance, healthcare, and critical infrastructure sectors prevalent in Europe, where data confidentiality is paramount. Additionally, the exposure of tokens could violate data protection regulations like GDPR if personal or sensitive data is indirectly accessed or disclosed. The lack of known exploits reduces immediate risk but does not eliminate the threat, especially given the medium CVSS score and ease of exploitation.

Summary

CVE-2026-25846 is a vulnerability identified in JetBrains YouTrack, a popular issue tracking and project management tool used by software development teams worldwide. The flaw exists in versions prior to 2025.3.119033 and involves the inadvertent exposure of access tokens within mailbox logs. This vulnerability is classified under CWE-532, which pertains to the exposure of sensitive information in logs. Access tokens are critical credentials that grant access to YouTrack resources and APIs; their exposure can lead to unauthorized access if intercepted by malicious actors. The vulnerability requires an attacker to have network access and low privileges (PR:L) but does not require user interaction (UI:N), making exploitation feasible in environments where attackers can monitor or access mailbox logs. The CVSS 3.1 base score is 6.5, indicating a medium severity level, with the vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N highlighting that the attack is network-based, with low complexity, requires privileges, no user interaction, unchanged scope, high confidentiality impact, and no impact on integrity or availability. No public exploits have been reported yet, but the risk remains significant due to the sensitive nature of access tokens. The vulnerability underscores the importance of secure logging practices, especially for sensitive authentication tokens, to prevent leakage through logs that may be accessible to unauthorized users or systems.

CWE-532Insertion of Sensitive Information into Log File (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A09:2025: Security Logging & Alerting Failures (opens in a new tab)
The product writes sensitive information to a log file.
Architecture and Design · Implementation
Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
Distribution
Remove debug log files before deploying the application into production.
Operation
Protect log files against unauthorized read/write.
OWASP Cheat Sheets
Application Logging Vocabulary (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V7.1.1 (opens in a new tab)
V7.1.2 (opens in a new tab)
V8.3.5 (opens in a new tab)
Attack patterns
Fuzzing for application mapping (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

jetbrains.com/privacy-security/issues-fixed/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Feb 2026, 13:34 UTC

WeaknessesCWE-532

Technical details

References

Community reviews

Related threats