dbcve.org
HubApplication · Jetbrains

CVE-2022-25260

CRITICAL · 9.1 CVSS v3.1 Published 2022-02-25
Fix available
A fix is available. Upgrade to 2021.1.14276 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
JetBrains Hub before 2021.1.14276 was vulnerable to blind Server-Side Request Forgery (SSRF).

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 · high confidence

JetBrains Hub before version 2021.1.14276 contains a blind Server-Side Request Forgery (SSRF) vulnerability. This allows an attacker to induce the server to make arbitrary requests to internal or external resources, potentially accessing internal services, bypassing network restrictions, or performing reconnaissance. The 'blind' nature means the attacker may not receive direct responses but can still trigger server-side requests.

MitigationUpgrade JetBrains Hub to version 2021.1.14276 or later to remediate this vulnerability. Apply the standard JetBrains upgrade procedure and verify core functionality post-upgrade.

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
HubApplication
Affected:< 2021.1.14276

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.

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 checks

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

  1. Identify if JetBrains Hub is installed
    Locate the Hub installation directory or check running services for a JetBrains Hub instance. Common locations include /opt/jetbrains/hub, /usr/local/hub, or the service manager listing (systemctl list-units | grep hub or similar).
    Affected if JetBrains Hub is found running in the environment
  2. Determine the installed version
    Check the Hub version. This can typically be found in the Hub admin UI under 'About' or 'Version', in startup logs, or by querying the /api/about endpoint if the web interface is accessible.
    Affected if The version cannot be determined or is lower than 2021.1.14276
  3. Compare version against the affected range
    Review the installed version number. Affected versions are any build prior to 2021.1.14276. Compare your build number to this threshold.
    Affected if Installed version is below 2021.1.14276 (for example, 2021.1.14250 or any 2020.x release)
  4. Check network exposure of Hub service
    Review network configuration to determine if the Hub service is exposed to untrusted networks. Verify firewall rules, reverse proxy settings, and whether the Hub management port is internet-facing.
    Affected if Hub is accessible from outside the trusted network and version is below 2021.1.14276

A user is affected if JetBrains Hub is running and the installed version is any build number lower than 2021.1.14276, particularly if the service is network-accessible.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2021.1.14276 or later
Fixed in 2021.1.14276
Interim mitigation

Upgrade JetBrains Hub to version 2021.1.14276 or later to remediate this vulnerability. Apply the standard JetBrains upgrade procedure and verify core functionality post-upgrade.

Recommended fix High confidence

2021.1.14276 or later (recommended: latest stable release)

  1. Back up the Hub database and configuration files before proceeding
  2. Stop the JetBrains Hub service
  3. Download the latest stable version of JetBrains Hub from the official JetBrains website (https://www.jetbrains.com/hub/download/)
  4. Install the new version following the standard upgrade procedure for your deployment method (installer or manual extraction)
  5. Start the JetBrains Hub service
  6. Verify the upgrade was successful by checking the Hub version in the administration console
  7. Confirm the vulnerability is resolved by verifying the version is 2021.1.14276 or later
Caveat Review JetBrains Hub release notes for version 2021.1.x for any breaking changes specific to your configuration and plugins

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

Fix this in Hub Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-25260 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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