CVE-2025-59455

MediumCVSS 4.2/10Last modified Jun 17, 2026

Description

In JetBrains TeamCity before 2025.07.2 project isolation bypass was possible due to race condition

Metrics

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

Weakness enumeration

CWE-362

Affected software

No affected versions have been published.

Timeline

Published
Sep 17, 2025
Last modified
Jun 17, 2026
NVD status
Analyzed

Related CVEs from 2025

CVE-2025-594565.5In JetBrains TeamCity before 2025.07.2 path traversal was possible during project archive uploadCVE-2025-594577.7In JetBrains TeamCity before 2025.07.2 missing Git URL validation allowed credential leakage on WindowsCVE-2025-594589.8In JetBrains Junie before 252.284.66, 251.284.66, 243.284.66, 252.284.61, 251.284.61, 243.284.61, 252.284.50, 252.284.54, 251.284.54, 251.28CVE-2025-594597.5An attacker that gains SSH access to an unprivileged account may be able to disrupt services (including SSH), causing persistent loss of avaCVE-2025-59467.2Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in Centreon Infra Monitoring (PolleCVE-2025-594607.5The system is deployed in its default state, with configuration settings that do not comply with the latest best practices for restricting aCVE-2025-594619.8A remote unauthenticated attacker may use the unauthenticated C++ API to access or modify sensitive data and disrupt services.CVE-2025-594627.5An attacker who tampers with the C++ CLI client may crash the UpdateService during file transfers, disrupting updates and availability.CVE-2025-594637.5An attacker may cause chunk-size mismatches that block file transfers and prevent subsequent transfers.CVE-2025-594647.5A memory leak in Node.js’s OpenSSL integration occurs when converting `X.509` certificate fields to UTF-8 without freeing the allocated buffCVE-2025-594657.5A malformed `HTTP/2 HEADERS` frame with oversized, invalid `HPACK` data can cause Node.js to crash by triggering an unhandled `TLSSocket` erCVE-2025-594667.5We have identified a bug in Node.js error handling where "Maximum call stack size exceeded" errors become uncatchable when `async_hooks.crea