Cyber Resilience

CVE-2025-47850

Access Control in Jetbrains Youtrack ≤ 2025.1.74704

Published
20 May 2025
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 4.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS Score 0.0031 24th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2025-47850 is a medium-severity Missing Authentication for Critical Function (CWE-306) vulnerability in Jetbrains Youtrack. Its CVSS base score is 4.3 (Medium).

Operationally, ranked at the 24th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

In JetBrains YouTrack before 2025.1.74704 restricted attachments could become visible after issue cloning

CWE(s)

Related Threats

CVEs Like This One

CVE-2025-48391Same product: Jetbrains Youtrack
CVE-2024-54155Same product: Jetbrains Youtrack
CVE-2024-54153Same product: Jetbrains Youtrack
CVE-2024-54156Same product: Jetbrains Youtrack
CVE-2026-57922Same product: Jetbrains Youtrack
CVE-2024-28228Same product: Jetbrains Youtrack
CVE-2026-57921Same product: Jetbrains Youtrack
CVE-2024-50574Same product: Jetbrains Youtrack
CVE-2023-35054Same product: Jetbrains Youtrack
CVE-2024-50579Same product: Jetbrains Youtrack

Affected Assets

jetbrains
youtrack
≤ 2025.1.74704

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • AC-3 Access Enforcement
  • AC-4 Information Flow Enforcement
  • AC-6 Least Privilege
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 6 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V6.2.3
  • V6.4.4
  • V10.4.16
  • V12.1.3

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly enforces access restrictions on attachments so that cloning an issue cannot expose objects whose visibility was previously limited.

prevent

Enforces information-flow rules between issue objects, ensuring restricted attachment content is not propagated to the clone.

prevent

Limits the privileges of the cloning operation so it cannot bypass the original attachment access policy.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-03 full match
prevents

Directly requires authentication of users/services/hardware, which eliminates missing authentication for critical functions.

PR.AA-01 partial match
prevents

Managing identities and credentials is a prerequisite for authentication but does not itself enforce it on critical functions.

PR.AA-05 partial match
prevents

Defining and enforcing authorizations assumes prior authentication and therefore only partially mitigates the absence of authentication.

PR.IR-01 partial match
prevents

Protecting networks from unauthorized access can be undermined by missing authentication but does not address the root authentication gap.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

The control explicitly calls for authentication before any critical function is reached, eliminating the possibility of bypassing authentication for high-value operations.

prevents

Mandating authentication requirements for critical functions at the requirements-gathering stage ensures that essential operations are not left unprotected by missing login or verification mechanisms.

mitigates

Mandating authentication for network services and critical functions stops attackers from invoking sensitive operations without credentials, closing gaps where authentication is absent for important capabilities.

prevents

Security engineering principles insist on authentication and authorization for every critical function, eliminating entry points that lack any access control mechanism.

none

Requiring strong authentication and access-privilege enablement for remote connections ensures that critical functions cannot be invoked without proper verification, closing a gap that would otherwise allow unauthenticated use.

none

Mandatory use of access cards, biometrics, or two-factor authentication ensures that critical physical areas cannot be entered without proper authentication.

References