CVE-2026-100273

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

GHSA-3c9g-jqwf-qrr8 ↗EUVD-2026-90017 ↗

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 YouTrack < 2026.2.19197
fixed in 2026.2.19197
CWE-863 Incorrect Authorization
ETK-2026-128, permanent identifier
20d 09h 46msince last run
35mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+8h19m
0
+2h
+4h
+6h
+10h
+12h

description

JetBrains YouTrack versions before 2026.2.19197 are affected by an authorization bypass in the scripts debugger. An attacker may use the bypass to execute arbitrary code through that component; the advisory does not provide further preconditions.

mitigation

Upgrade JetBrains YouTrack to version 2026.2.19197 or later. Restrict access to the scripts debugger until the update is applied.

fixed in 2026.2.19197

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.30%21st percentile
agent run time
35m
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
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-128",
  "cve_id": "CVE-2026-100273",
  "display_id": "CVE-2026-100273",
  "ghsa_id": "GHSA-3c9g-jqwf-qrr8",
  "euvd_id": "EUVD-2026-90017",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authorization bypass in the YouTrack scripts debugger",
  "summary": "JetBrains YouTrack versions before 2026.2.19197 are affected by an authorization bypass in the scripts debugger. An attacker may use the bypass to execute arbitrary code through that component; the advisory does not provide further preconditions.",
  "mitigation": "Upgrade JetBrains YouTrack to version 2026.2.19197 or later. Restrict access to the scripts debugger until the update is applied.",
  "vendor": "JetBrains",
  "product": "YouTrack",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 2026.2.19197"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2026.2.19197"
      ],
      "package_name": "YouTrack",
      "purl": null
    }
  ],
  "cwes": [
    863
  ],
  "cvss_score": 8.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N",
  "epss_score": 0.003,
  "epss_percentile": 0.2155,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 34.930183283333335,
  "t0_at": "2026-09-30T15:17:53.525000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-09-30T15:17:53.525000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-30T15:17:53.525000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-100273"
    }
  }
}

published 2026-09-30 16:48Z
last change 2026-10-21 08:40Z

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.