YoutrackApplication · Jetbrains

CVE-2026-49368

MEDIUM · 5.4 CVSS v3.1 Published 2026-05-29

Fix available

A fix is available. Upgrade to 2026.1.13162 or later.

See remediation →

58/100

Remediation priority · Elevated

Remotely reachable

Official description

NVD · unedited

In JetBrains YouTrack before 2026.1.13162 stored XSS in project notification templates was possible

Technical summary

dbcve analysis · high confidence

Stored cross-site scripting (XSS) vulnerability in JetBrains YouTrack's project notification templates allows attackers to inject malicious scripts that execute when users view notifications. The vulnerability exists because user-controlled input in notification templates is not properly sanitized before rendering.

MitigationUpgrade YouTrack to version 2026.1.13162 or later to patch the stored XSS vulnerability in project notification templates.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

YoutrackApplication

Affected:< 2026.1.13162

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: Low
User interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

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

Am I affected?

dbcve checks

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

Identify the installed YouTrack version

Access the YouTrack administration area and navigate to the 'About' section, or check the build number in the footer of any YouTrack page. Compare this version number to 2026.1.13162.

Affected if The installed version is less than 2026.1.13162 (for example, 2026.1.12345 or any 2025.x.x version).
Determine if notification templates are in use

Navigate to Project Settings > Notifications in YouTrack. Check whether any project notification rules and templates have been configured or are active.

Affected if Notification templates are actively configured for one or more projects.
Review notification templates for unexpected content

Examine each notification template in the project notification settings. Look for HTML script tags, JavaScript event handlers (onload, onclick, onerror), or unusual encoded characters that may indicate injected code.

Affected if Any notification template contains script tags, javascript: URLs, or suspicious JavaScript event handlers.
Check audit logs for recent template modifications

In YouTrack, go to System > Audit Log and search for events related to 'notification template' or 'notification rule' modifications. Note any unexpected or unauthorized changes.

Affected if There are recent changes to notification templates that were not made by known administrators.

You are affected if your YouTrack version is below 2026.1.13162 AND you have notification templates configured in your projects.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to 2026.1.13162 or later

Fixed in 2026.1.13162

Interim mitigation

Upgrade YouTrack to version 2026.1.13162 or later to patch the stored XSS vulnerability in project notification templates.

Recommended fix High confidence

YouTrack 2026.1.13162 or later

Back up your YouTrack database and configuration before upgrading
Download YouTrack version 2026.1.13162 or later from the official JetBrains website (www.jetbrains.com/youtrack)
Stop the YouTrack service
Follow the standard YouTrack upgrade procedure for your deployment type (standalone or InCloud)
Start the YouTrack service after upgrade completes
Verify the upgrade was successful and test that project notification templates work correctly

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

Fix this in Youtrack Scoped from the published advisory

Consultation1.0 h
Implementation2.0 h
Testing2.0 h
Review / QA1.0 h

6.0 hours of engineering $1,040

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-49368 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

www.jetbrains.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2026-49368?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to 2026.1.13162 or later

Severity 5.4 Medium

Exploit likelihood EPSS, next 30 days 0.2%

Affects: Youtrack

Remediation

Need this fixed?

Fix this in Youtrack 6 hrs · Low

Typical engagement from $1,040

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2026-49368 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References