Threats / JetBrains / CVE-2024-27199
CVE-2024-27199
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-11
JetBrains TeamCity vulnerability
JetBrains TeamCity contains a relative path traversal vulnerability enabling limited admin actions. Actively exploited in ransomware campaigns.
Verdict
Today item, not a backlog item.
A path traversal flaw in TeamCity allows attackers to bypass access controls and perform restricted administrative operations. Active exploitation in ransomware campaigns indicates high real-world risk despite functional limitations.
CISA KEV Yes · 2026-04-205Ransomware use Flagged5EPSS 0.99991 (verify live)6Exploit Weaponized · public PoC7CVSS 7.33CISA SSVC Exploitation: active · Automatable: yes · Impact: partial4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
471 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-04-20), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.99991 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L) · Affected: JetBrains, TeamCity. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-23 Relative Path Traversal — weakness family: Path traversal / file.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: partialCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 777 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious request using relative path sequences to traverse the file system and access restricted administrative functions.
Business
Unauthorized administrative capabilities are exposed, creating a foothold for privilege escalation and system compromise.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I leverage the path traversal to perform limited admin actions without proper authentication or authorization checks.
Business
Access controls fail, allowing attackers to modify configurations, create accounts, or alter deployment pipelines.
3
Lateral reach — past segmentation narrative 3
Attacker
I use the compromised admin access to establish persistence or deploy ransomware payloads across the CI/CD infrastructure.
Business
Build systems and deployment infrastructure become vectors for enterprise-wide ransomware distribution and operational shutdown.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by JetBrainsCNA
Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.