CVE-2025-67739
Jetbrains Teamcity ≤ 2025.11.2
Raw vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:NSummary
CVE-2025-67739 is a low-severity Improper Authorization in Handler for Custom URL Scheme (CWE-939) vulnerability in Jetbrains Teamcity. Its CVSS base score is 3.1 (Low).
Operationally, ranked at the 6th 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-6 (Least Privilege) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-202697
Vulnerability Data
In JetBrains TeamCity before 2025.11.2 improper repository URL validation could lead to local paths disclosure
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Access enforcement directly stops unauthorized actors from invoking the custom URL handler by requiring approved authorizations for that entry point.
Least privilege limits the authorizations granted to the handler, reducing the chance that any actor can invoke it without restriction.
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.
Defining, enforcing, and reviewing access permissions directly addresses the missing authorization checks for custom URL scheme handlers.
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.
Security testing can discover missing authorization checks, but does not itself implement the required controls.
Enforces explicit authorization checks on which actors may invoke handlers, directly addressing the missing restriction on custom-URL-scheme access.
High-level access-control policy provides governance context but does not prescribe the technical authorization logic needed for URL-scheme handlers.
Requires security requirements that define which callers are permitted to trigger custom URL handlers, mitigating the authorization gap.
Mandates secure coding practices that include proper authorization checks before executing actions triggered by custom URL schemes.