CVE-2026-132900

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

EUVD-2026-129665 ↗

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.1, < 2026.1.4; < 2025.11.8
fixed in 2026.1.4, 2025.11.8
CWE-201 Insertion of Sensitive Information Into Sent Data
ETK-2026-4923Zero's internal tracking ID, independent of the CVE number., permanent identifier
7h 13msince last run
1h 13mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+2h16m
0
+4h
+6h
+8h
+10h
+12h

description

TeamCity pipeline handling can expose protected parameter data in affected releases. A user able to view a project may obtain values intended to remain secret through pipeline access.

mitigation

Upgrade TeamCity to 2026.1.4 or 2025.11.8, or to a newer supported release. Until upgraded, restrict project-viewer access and rotate any parameters that may have been exposed.

fixed in 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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
1h 13m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-19 10:32Z
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-19 10:32Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4923",
  "cve_id": "CVE-2026-132900",
  "display_id": "CVE-2026-132900",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-129665",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Secure parameter information disclosure in TeamCity",
  "summary": "TeamCity pipeline handling can expose protected parameter data in affected releases. A user able to view a project may obtain values intended to remain secret through pipeline access.",
  "mitigation": "Upgrade TeamCity to 2026.1.4 or 2025.11.8, or to a newer supported release. Until upgraded, restrict project-viewer access and rotate any parameters that may have been exposed.",
  "vendor": "JetBrains",
  "product": "TeamCity",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 2026.1, < 2026.1.4",
        ">= 0, < 2025.11.8"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2026.1.4",
        "2025.11.8"
      ],
      "package_name": "TeamCity",
      "purl": null
    }
  ],
  "cwes": [
    201
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 72.55340763333334,
  "t0_at": "2026-11-19T10:32:48.948000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-19T10:32:48.948000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-19T10:32:48.948000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-132900"
    }
  }
}

published 2026-11-19 11:36Z
last change 2026-11-19 19:37Z

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.