CVE-2025-47850
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 2025.1.74704 restricted attachments could become visible after issue cloning
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 confidenceThis is an information disclosure vulnerability in JetBrains YouTrack where restricted attachments become visible after an issue is cloned. The cloning operation fails to preserve the original attachment access restrictions, allowing users who should not have access to view the attachments.
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< 2025.1.74704CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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.
-
Check YouTrack versionLog into YouTrack as an administrator and navigate to Administration > Products > YouTrack, or access the /api/admin/products endpoint to retrieve the installed version number.Affected if The installed version is lower than 2025.1.74704 (e.g., 2025.1.x versions below 74704, or any 2024.x or earlier version).
-
Identify cloned issues with attachmentsReview the issue audit history or activity log for cloned issues. Check if any issues containing attachments were cloned to another project. Use the issue search: created:{last 30d} and inspect issues with the 'clone' activity entry.Affected if Any issues with restricted attachments were cloned within the timeframe the vulnerability existed (before version 2025.1.74704).
-
Verify attachment access restrictions on cloned issuesOn cloned issues that originated from issues with restricted attachments, inspect the attachment permissions. Navigate to the attachment and check if it shows as accessible to users who should not have access based on the original restriction settings.Affected if Users who were not granted access to the original attachment can now view the attachment on the cloned issue.
You are affected if your YouTrack version is below 2025.1.74704 AND any issues with restricted attachments have been cloned to other projects, exposing those attachments to unauthorized users.
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 · scoped2025.1.74704
Upgrade YouTrack to version 2025.1.74704 or later. Until then, avoid cloning issues that contain sensitive attachments.
2025.1.74704
- Download YouTrack version 2025.1.74704 or later from the official JetBrains website
- Perform a full backup of your YouTrack database and configuration before upgrading
- Stop the YouTrack service
- Install the upgrade following JetBrains standard upgrade procedures
- Start the YouTrack service after installation
- Verify that restricted attachments in cloned issues are no longer accessible without proper authorization
- Review audit logs for any suspicious access patterns that may have occurred prior to the patch
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47850 — 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-2025-47850 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