CVE-2026-100277

validatedZero produced an exploit or a check.

GHSA-mqhr-7f7q-h475 ↗EUVD-2026-90021 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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-126, permanent identifier
+1h31mTTV
45mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0mcheck available+91magent stopped
0
+30min
+60min

description

JetBrains YouTrack versions before 2026.2.19197 do not adequately prevent reuse of notification signatures. An attacker who can replay a valid notification signature may take over an account.

mitigation

Upgrade JetBrains YouTrack to version 2026.2.19197 or later.

fixed in 2026.2.19197

check
available
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.
0.28%19th percentile
agent run time
45m
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 check: a technique exists and was validated, 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-100277

{
  "etk_id": "ETK-2026-126",
  "cve_id": "CVE-2026-100277",
  "display_id": "CVE-2026-100277",
  "ghsa_id": "GHSA-mqhr-7f7q-h475",
  "euvd_id": "EUVD-2026-90021",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Notification signature replay in JetBrains YouTrack",
  "summary": "JetBrains YouTrack versions before 2026.2.19197 do not adequately prevent reuse of notification signatures. An attacker who can replay a valid notification signature may take over an account.",
  "mitigation": "Upgrade JetBrains YouTrack to version 2026.2.19197 or later.",
  "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.9,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L",
  "epss_score": 0.0028,
  "epss_percentile": 0.1954,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 45.44404243333334,
  "t0_at": "2026-09-30T15:17:55.036000+00:00",
  "signals": {
    "check": {
      "at": "2026-09-30T16:49:24.931086+00:00",
      "days": 0.06354045238425926,
      "is_lower_bound": false,
      "measured_at": "2026-09-30T15:17:55.036000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-09-30T15:17:55.036000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-30T15:17:55.036000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-100277"
    }
  }
}

published 2026-09-30 15:59Z
last change 2026-10-21 07:48Z

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.