LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25848: In JetBrains Hub before 2025.3.119807 authentication bypass allowing administrative actions was possible

In JetBrains Hub before 2025.3.119807 authentication bypass allowing administrative actions was possible

CriticalCVSS 9.1Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

JetBrains Hub versions before 2025.3.119807 have an authentication bypass that could allow administrative actions without logging in. For organizations using Hub, this is high business urgency because unauthorized administration can affect user, project, and access-management workflows. No provided source confirms active exploitation.

Executive priority

Prioritize remediation immediately for any active JetBrains Hub deployment. This is a critical unauthenticated admin-action issue, but current provided evidence does not confirm exploitation in the wild. Patch first, then validate exposure and review administrative activity.

Technical view

CVE-2026-25848 is a CWE-306 missing authentication issue in JetBrains Hub before 2025.3.119807. CVSS 3.1 is 9.1: network-accessible, low complexity, no privileges, no user interaction, with high confidentiality and integrity impact and no availability impact stated.

Likely exposure

Exposure is likely limited to organizations running JetBrains Hub before 2025.3.119807, especially if the Hub instance is reachable over internal or external networks. The provided affected-version data is sparse, so confirm product/version directly against JetBrains guidance.

Exploitation context

The record describes authentication bypass enabling administrative actions. The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation or public exploit availability. Treat internet-exposed Hub instances as urgent due to unauthenticated network attack conditions.

Researcher notes

Evidence is concise: the CVE description and JetBrains reference identify the flaw and fixed-before boundary. The affected entry in the bundle is not detailed beyond Hub and version context. Do not assume additional JetBrains products are affected without vendor confirmation.

Mitigation direction

  • Upgrade JetBrains Hub to 2025.3.119807 or later.
  • Review JetBrains fixed-issues guidance for any environment-specific instructions.
  • Restrict Hub network exposure until patched, where operationally feasible.
  • Prioritize externally reachable or identity-critical Hub instances first.

Validation and detection

  • Inventory all JetBrains Hub deployments and owners.
  • Verify each Hub instance version is 2025.3.119807 or later.
  • Confirm whether any Hub instance is internet-accessible.
  • Review administrative activity logs for unexpected changes.
  • Track remediation status in vulnerability management records.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-306: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-25848 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N3.95.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.1Critical
CVSS 3.1 vector shape for CVE-2026-25848Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
JetBrainsHub0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-306 · source CWE mapping

Missing Authentication for Critical Function

Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.