YoutrackApplication · Jetbrains

CVE-2026-61492

MEDIUM · 6.1 CVSS v3.1 Published 2026-07-10
Fix available
A fix is available. Upgrade to 2026.2.17394 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 6 weeks old

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 · unedited
In JetBrains YouTrack before 2026.2.17394 stored XSS via article titles in digest emails was possible

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 confidence

Stored XSS vulnerability in JetBrains YouTrack allows attackers to inject malicious JavaScript through article titles in digest emails. The payload is stored in the application and rendered unsanitized when users receive digest emails, enabling session hijacking or phishing via the email channel.

MitigationUpgrade YouTrack to version 2026.2.17394 or later. Until then, disable digest emails or implement email content filtering as a temporary workaround.

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
YoutrackApplication
Affected:< 2026.2.17394

CVSS 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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify YouTrack version
    Navigate to YouTrack administration interface or query the /api/debug/version endpoint to retrieve the installed version number
    Affected if The installed version is lower than 2026.2.17394
  2. Confirm digest email feature is enabled
    Access YouTrack administration settings and locate the digest or notification email configuration section to verify whether digest emails are turned on
    Affected if Digest email delivery is enabled in the YouTrack configuration
  3. Review article titles for suspicious content
    Examine knowledge base articles and any content items that can appear in digest emails. Inspect article title fields for unescaped HTML, script tags, or JavaScript event handlers
    Affected if Any stored article titles contain raw HTML or JavaScript that would execute when rendered in emails

You are affected if your YouTrack version is below 2026.2.17394 and digest emails are enabled, allowing stored XSS payloads in article titles to execute in email recipients browsers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2026.2.17394 or later
Fixed in 2026.2.17394
Interim mitigation

Upgrade YouTrack to version 2026.2.17394 or later. Until then, disable digest emails or implement email content filtering as a temporary workaround.

Recommended fix High confidence

YouTrack 2026.2.17394 or later

  1. 1. Back up your YouTrack database and configuration files before upgrading
  2. 2. Download YouTrack version 2026.2.17394 or later from the official JetBrains website (www.jetbrains.com/youtrack/download)
  3. 3. Stop the YouTrack service
  4. 4. Run the installer or deploy the new version following JetBrains upgrade documentation
  5. 5. Verify the upgrade was successful by logging into YouTrack
  6. 6. Test that article titles in digest emails are properly sanitized and no longer allow XSS execution
Caveat Review JetBrains release notes for 2026.2.x for any breaking changes between your current version and the target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Youtrack Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-61492 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-61492 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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