CVE-2021-37549
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 · uneditedIn JetBrains YouTrack before 2021.1.11111, sandboxing in workflows was insufficient.
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 · moderate confidenceInsufficient sandboxing in YouTrack's workflow engine prior to version 2021.1.11111 allows authenticated users to potentially escape the workflow sandbox and execute arbitrary code or access restricted resources, as indicated by the critical CVSS score of 9.1.
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< 2021.1.11111CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed YouTrack versionNavigate to the YouTrack administration area or check the build number in the application footer. Alternatively, access the /api/serverInfo endpoint or check the youtrack.jar file properties if on-premise.Affected if The installed version number is lower than 2021.1.11111
-
Confirm workflow engine is accessibleVerify that the YouTrack workflow functionality is enabled and accessible. Check in Administration > Workflows to see if users have access to create, edit, or run custom workflows.Affected if Authenticated users have the ability to create, modify, or execute custom workflows in YouTrack
-
Check for custom or third-party workflowsReview the list of installed workflows in Administration > Workflows. Look for any user-created or imported workflows that could be exploited to escape the sandbox.Affected if Any custom workflows exist that could potentially be manipulated to leverage the sandbox escape
You are affected if YouTrack version is below 2021.1.11111 and authenticated users have access to the workflow engine functionality.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2021.1.11111
Upgrade YouTrack to version 2021.1.11111 or later to address the insufficient sandboxing in the workflows functionality.
YouTrack 2021.1.11111 or later
- 1. Back up your YouTrack database and configuration files before upgrading
- 2. Download YouTrack version 2021.1.11111 or later from the JetBrains website or your subscription portal
- 3. Stop the YouTrack service
- 4. Install the new version following JetBrains upgrade documentation
- 5. Verify the workflow sandboxing is functioning correctly after upgrade
- 6. Test existing workflows to ensure functionality is preserved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-37549 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-37549 in production — separate from our analysis above.
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.
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.
- 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