CVE-2024-27199

CRITICALNVD 7.39.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2026-04-20), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.3 retained for reference. The 9.0 is the floor for confirmed exploitation, not an impact rating: this CVE's impact severity (EG Severity) is CVSS 7.3 HIGH under GitHub Security Advisory CVSS. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekExploited in the wild

Also known asEUVD-2024-24438 (ENISA EUVD) · GHSA-m7gg-q7qj-3r2r (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictMitigate nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
CISA-KEV: ExploitedEPSS PROB: >99.9%CVSS: 7.3Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (JetBrains s.r.o.) lists JetBrains TeamCity versions before 2023.11.4 as affected. No release containing a fix is confirmed on record.

In JetBrains TeamCity before 2023.11.4 path traversal allowing to perform limited admin actions was possible

CVSS v3
7.3
EG Score
9.0CRITICALhigh confidence
EG Risk
88
EG Risk 88/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity73% × 45%
Impact severity (EG Severity): CVSS 7.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Attend at low or medium mission impact; Act at high (mission-essential systems).
Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation sooner than your normal schedule at low or medium mission impact and as soon as possible at high.
EPSS PROB
>99.9%
EPSS %ILE
99th
KEV
⚠ Exploited

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is the CISA KEV floor for confirmed exploitation, not an impact rating: its impact severity (EG Severity) is CVSS 7.3 HIGH.

EG Severity
7.3 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
>99.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Attend at medium mission impactAttend at low or medium mission impact; Act at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 14 days if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: this CVE is in CISA's KEV catalog, and CISA's required action for it, quoted below, applies whether or not a fix is released.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Attend at low or medium mission impact; Act at high (mission-essential systems).

No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation sooner than your normal schedule at low or medium mission impact and as soon as possible at high.

Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 14 days if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: this CVE is in CISA's KEV catalog, and CISA's required action for it, quoted below, applies whether or not a fix is released.

The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA required action“Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://www.jetbrains.com/privacy-security/issues-fixed/ · https://blog.jetbrains.com/teamcity/2024/03/additional-critical-security-issues-affecting-teamcity-on-premises-cve-2024-27198-and-cve-2024-27199-update-to-2023-11-4-now/ · https://nvd.nist.gov/vuln/detail/CVE-2024-27199

Published

March 4, 2024

Last Modified

April 21, 2026

Advisory Details (4)

Auto-updated Nov 2, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). No fix on record yet. Sources: cisa.
CISA🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-27199
Web page

RCity-CVE-2024-27198/RCity.py at main · Stuub/RCity-CVE-2024-27198 · GitHub

https://github.com/Stuub/RCity-CVE-2024-27198/blob/main/RCity.py
Web page

Fixed security issues

https://www.jetbrains.com/privacy-security/issues-fixed/
Web page

JetBrains TeamCity Mass Exploitation Underway, Rogue Accounts Thrive

https://www.darkreading.com/cyberattacks-data-breaches/jetbrains-teamcity-mass-exploitation-underway-rogue-accounts-thrive

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 103× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 992 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 892 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 10:40 UTCEG score recompute
  2. 2026-11-02 10:40 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  3. 2026-11-01 11:41 UTCEG score recompute
  4. 2026-11-01 11:41 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  5. 2026-10-31 12:42 UTCEG score recompute
  6. 2026-10-31 12:42 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  7. 2026-10-30 13:43 UTCEG score recompute
  8. 2026-10-30 13:43 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  9. 2026-10-29 14:44 UTCEG score recompute
  10. 2026-10-29 14:44 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  11. 2026-10-28 16:29 UTCEPSS rescoreEPSS >99.9% · 99th percentile
  12. 2026-10-28 15:46 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  13. 2026-10-27 16:47 UTCEG score recompute
  14. 2026-10-27 16:47 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  15. 2026-10-26 17:47 UTCEG score recompute
  16. 2026-10-26 17:47 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  17. 2026-10-25 18:45 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  18. 2026-10-25 17:15 UTCEG score recompute
  19. 2026-10-24 19:43 UTCEG score recompute
  20. 2026-10-24 19:43 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  21. 2026-10-23 20:44 UTCEG score recompute
  22. 2026-10-23 20:44 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  23. 2026-10-22 21:45 UTCEG score recompute
  24. 2026-10-22 21:45 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  25. 2026-10-21 22:46 UTCEG score recompute
Show 75 more
  1. 2026-10-21 22:46 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  2. 2026-10-20 23:47 UTCEG score recompute
  3. 2026-10-20 23:47 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  4. 2026-10-20 00:47 UTCEG score recompute
  5. 2026-10-20 00:47 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  6. 2026-10-19 01:47 UTCEG score recompute
  7. 2026-10-19 01:47 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  8. 2026-10-18 07:22 UTCEG score recompute
  9. 2026-10-18 02:47 UTCEG score recompute
  10. 2026-10-18 02:46 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  11. 2026-10-17 03:46 UTCEG score recompute
  12. 2026-10-17 03:46 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  13. 2026-10-16 04:46 UTCEG score recompute
  14. 2026-10-16 04:46 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  15. 2026-10-15 05:45 UTCEG score recompute
  16. 2026-10-15 05:44 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  17. 2026-10-14 06:42 UTCEG score recompute
  18. 2026-10-14 06:42 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  19. 2026-10-13 07:42 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  20. 2026-10-12 17:59 UTCEG score recompute
  21. 2026-10-12 08:43 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  22. 2026-10-12 04:53 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  23. 2026-10-12 01:05 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  24. 2026-10-11 21:18 UTCEG score recompute
  25. 2026-10-11 21:18 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  26. 2026-10-11 17:31 UTCEG score recompute
  27. 2026-10-11 17:30 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  28. 2026-10-11 13:41 UTCEG score recompute
  29. 2026-10-11 13:41 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  30. 2026-10-11 09:53 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  31. 2026-10-11 06:04 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  32. 2026-10-11 02:17 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  33. 2026-10-10 22:27 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  34. 2026-10-10 18:40 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  35. 2026-10-10 14:53 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  36. 2026-10-10 11:07 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  37. 2026-10-10 07:20 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  38. 2026-10-10 03:33 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  39. 2026-10-09 23:46 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  40. 2026-10-09 19:59 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  41. 2026-10-09 16:12 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  42. 2026-10-09 12:26 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  43. 2026-10-09 08:38 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  44. 2026-10-09 04:50 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  45. 2026-10-09 01:04 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  46. 2026-10-08 21:17 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  47. 2026-10-08 17:31 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  48. 2026-10-08 13:44 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  49. 2026-10-08 09:55 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  50. 2026-10-08 06:08 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  51. 2026-10-08 02:21 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  52. 2026-10-07 22:34 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  53. 2026-10-07 18:47 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  54. 2026-10-07 15:01 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  55. 2026-10-07 11:15 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  56. 2026-10-07 07:29 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  57. 2026-10-07 03:42 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  58. 2026-10-06 23:55 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  59. 2026-10-06 20:09 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  60. 2026-10-06 16:23 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  61. 2026-10-06 12:37 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  62. 2026-10-06 08:50 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  63. 2026-10-06 05:03 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  64. 2026-10-06 01:16 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  65. 2026-10-05 21:27 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  66. 2026-10-05 17:39 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  67. 2026-10-05 13:53 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  68. 2026-10-05 10:06 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  69. 2026-10-05 06:20 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  70. 2026-10-05 02:33 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  71. 2026-10-04 22:47 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  72. 2026-10-04 19:00 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  73. 2026-10-04 15:14 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  74. 2026-10-04 11:25 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3
  75. 2026-10-04 07:39 UTCGHSA enrichmentGHSA-m7gg-q7qj-3r2r · GitHub severity HIGH · GitHub CVSS 7.3

Public detection templates

(1 reference)

A public Nuclei detection template is referenced for this CVE. A detection template checks whether a system is affected; it is not necessarily exploit code.

  • Nucleihttp/cves/2024/CVE-2024-27199.yaml
    Published Mar 6, 2024

    TeamCity < 2023.11.4 - Authentication Bypass

    Open source ↗

Related CVEs(same CWE)

Frequently asked(6)

What is CVE-2024-27199?
CVE-2024-27199 is a critical-severity vulnerability; its CVE record was published on March 4, 2024. In JetBrains TeamCity before 2023.11.4 path traversal allowing to perform limited admin actions was possible
When was the CVE record for CVE-2024-27199 published?
The CVE record for CVE-2024-27199 was published on March 4, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 21, 2026; the record at its source may have been updated since.
Is CVE-2024-27199 actively exploited?
Yes. CISA added CVE-2024-27199 to the Known Exploited Vulnerabilities catalog on April 20, 2026, affecting JetBrains TeamCity. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation.
What is the CVSS score of CVE-2024-27199?
CVE-2024-27199 has a CVSS v3 base score of 7.3 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2024-27199?
CVE-2024-27199 affects JetBrains TeamCity.
How do I remediate CVE-2024-27199?
No fix for CVE-2024-27199 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (JetBrains s.r.o.) lists JetBrains TeamCity versions before 2023.11.4 as affected. No release containing a fix is confirmed on record.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-27199

Explore →

Is Your Infrastructure Affected by CVE-2024-27199?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs