CVE-2026-100254

waiting for further signalsZero needs more public information before it can validate it.

GHSA-6h2c-wm78-7wv3 ↗EUVD-2026-89998 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
JetBrains TeamCity < 2026.2; 2026.1.4; 2025.11.8
fixed in 2026.2, 2026.1.4, 2025.11.8
ETK-2026-160, permanent identifier
20d 12h 43msince last run
1h 17mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+7h44m
0
+2h
+4h
+6h
+10h
+12h

description

TeamCity versions earlier than 2026.2, 2026.1.4, and 2025.11.8 are affected in Pipeline Git connection settings. An authenticated user may execute commands on a Windows-hosted TeamCity server.

mitigation

Upgrade TeamCity to 2026.2, 2026.1.4, or 2025.11.8 as appropriate for the release line in use. Restrict access to trusted authenticated users until the update is applied.

fixed in 2026.2, 2026.1.4, 2025.11.8

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.47%39th percentile
agent run time
1h 17m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-30 15:17Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-09-30 15:17Z
    ghsa: trigger signal, started the run
  2. 2026-09-30 15:17Z

this entry in the feed

GET /api/v1/feed/CVE-2026-100254

{
  "etk_id": "ETK-2026-160",
  "cve_id": "CVE-2026-100254",
  "display_id": "CVE-2026-100254",
  "ghsa_id": "GHSA-6h2c-wm78-7wv3",
  "euvd_id": "EUVD-2026-89998",
  "status": "published",
  "anchor_state": "anchored",
  "title": "CRLF injection in TeamCity Pipeline Git connection settings",
  "summary": "TeamCity versions earlier than 2026.2, 2026.1.4, and 2025.11.8 are affected in Pipeline Git connection settings. An authenticated user may execute commands on a Windows-hosted TeamCity server.",
  "mitigation": "Upgrade TeamCity to 2026.2, 2026.1.4, or 2025.11.8 as appropriate for the release line in use. Restrict access to trusted authenticated users until the update is applied.",
  "vendor": "JetBrains",
  "product": "TeamCity",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 2026.2",
        "2026.1.4",
        "2025.11.8"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2026.2",
        "2026.1.4",
        "2025.11.8"
      ],
      "package_name": "TeamCity",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0047,
  "epss_percentile": 0.3949,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 77.24958428333333,
  "t0_at": "2026-09-30T15:17:45.316000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-09-30T15:17:45.316000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-30T15:17:45.316000+00:00",
      "url": "https://github.com/advisories/GHSA-6h2c-wm78-7wv3"
    }
  }
}

published 2026-09-30 21:44Z
last change 2026-10-21 10:52Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.