Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-56141 – Account Takeover via Predictable Recovery Codes – JetBrains Hub before 2026.1.13…

Be the first to know when new zero-days emerge:

Summary

CVE-2026-56141 is a critical (CVSS 9.8) account takeover vulnerability in JetBrains Hub, the on-premises centralized identity management and SSO platform used to authenticate developers across JetBrains tools such as YouTrack and TeamCity. The flaw arises from a cryptographically weak pseudo-random number generator (PRNG) used to produce account restore (recovery) codes, allowing an unauthenticated remote attacker to predict or brute-force a target user’s restore code and fully take over their account. No authentication or user interaction is required for exploitation.

Technical details

  • Root cause: JetBrains Hub generates account restore/recovery codes using a cryptographically weak PRNG (CWE-338), making the codes statistically predictable to an attacker with network access to the Hub instance.
  • Trigger conditions: An attacker needs only network access to an exposed Hub instance and knowledge of (or ability to enumerate) a valid username or account identifier; no credentials or session are required.
  • Attack vector: Fully remote and unauthenticated over the network (AV:N/AC:L/PR:N/UI:N). An attacker submits predicted restore codes against the Hub account recovery endpoint to bypass authentication entirely.
  • Impact: Complete account takeover — the attacker gains full control of the targeted user account, including confidentiality, integrity, and availability of all data and services accessible to that account. Compromise of an administrative Hub account gives an attacker control over the entire identity provider, including SSO sessions for connected JetBrains products.

Affected software

  • JetBrains Hub all versions prior to 2026.1.13757
  • JetBrains Hub all versions prior to 2025.3.148033 (2025.3 branch)
  • JetBrains Hub all versions prior to 2025.2.148048 (2025.2 branch)
  • JetBrains Hub all versions prior to 2025.1.148120 (2025.1 branch)
  • JetBrains Hub all versions prior to 2024.3.148430 (2024.3 branch)
  • JetBrains Hub all versions prior to 2024.2.148429 (2024.2 branch)

Severity

CVSS v3.1 Base Score: 9.8 (Critical)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate action — upgrade JetBrains Hub to one of the following patched builds corresponding to your current release branch:
    • 2026.1.13757
    • 2025.3.148033
    • 2025.2.148048
    • 2025.1.148120
    • 2024.3.148430
    • 2024.2.148429
  • If immediate patching is not possible: Restrict network access to the Hub instance to trusted IP ranges only, blocking unauthenticated internet access to the account recovery endpoint. Audit Hub access logs for unexpected recovery code submission attempts.
  • Invalidate and regenerate all existing restore/recovery codes for all user accounts after upgrading to a patched version.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge