CVE-2026-103493

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

GHSA-6qqm-669w-6778 ↗EUVD-2026-90584 ↗

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.19422
fixed in 2026.2.19422
CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
ETK-2026-230, permanent identifier
19d 00h 09msince last run
39mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+20h22m
0
+2h
+4h
+6h
+8h
+10h

description

JetBrains YouTrack versions before 2026.2.19422 are affected by stored cross-site scripting in Mermaid and LaTeX content. An attacker able to store malicious content may cause script execution when another user views the affected content.

mitigation

Upgrade YouTrack to version 2026.2.19422 or later. Until upgraded, restrict untrusted users from creating or modifying Mermaid and LaTeX content where feasible.

fixed in 2026.2.19422

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.
0.22%11th percentile
agent run time
39m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-01 09:15Z
Δ 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-10-01 09:15Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-230",
  "cve_id": "CVE-2026-103493",
  "display_id": "CVE-2026-103493",
  "ghsa_id": "GHSA-6qqm-669w-6778",
  "euvd_id": "EUVD-2026-90584",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Stored cross-site scripting in JetBrains YouTrack",
  "summary": "JetBrains YouTrack versions before 2026.2.19422 are affected by stored cross-site scripting in Mermaid and LaTeX content. An attacker able to store malicious content may cause script execution when another user views the affected content.",
  "mitigation": "Upgrade YouTrack to version 2026.2.19422 or later. Until upgraded, restrict untrusted users from creating or modifying Mermaid and LaTeX content where feasible.",
  "vendor": "JetBrains",
  "product": "YouTrack",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 2026.2.19422"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2026.2.19422"
      ],
      "package_name": "YouTrack",
      "purl": null
    }
  ],
  "cwes": [
    79
  ],
  "cvss_score": 8.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N",
  "epss_score": 0.0022,
  "epss_percentile": 0.1192,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 38.61229825,
  "t0_at": "2026-10-01T09:15:26.048000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-01T09:15:26.048000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-01T09:15:26.048000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-103493"
    }
  }
}

published 2026-10-01 10:57Z
last change 2026-10-21 04:45Z

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.