CVE-2025-67740 json
In JetBrains TeamCity before 2025.11 improper access control could expose GitHub App token's metadata
published 10mo ago modified last mo. also EUVD-2025-202696
- cvss
- 2.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 12%
- public exploits
- 0
- none known
Summary
In JetBrains TeamCity before 2025.11 improper access control could expose GitHub App token's metadata
Patch / fix
- JetBrains TeamCity 2025.11
Is CVE-2025-67740 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 10mo ago
Exploit prediction
0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 2.7 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N |
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected products
- JetBrains TeamCity
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
References
-
jetbrains.com
/privacy-security/issues-fixed/
issue-tracking, vendor-advisory
Sources
- CVE List CVE-2025-67740
- NVD CVE-2025-67740
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.