CVE-2026-108545

validatedZero produced an exploit or a check.

GHSA-g54j-r2jq-rm6q ↗EUVD-2026-96340 ↗

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.
SillyTavern >= 1.12.13, <= 1.19.0
CWE-400 Uncontrolled Resource Consumption
ETK-2026-1171Zero's internal tracking ID, independent of the CVE number., permanent identifier
+1h25mTTV
24mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0mcheck available+85magent stopped
0
+30min
+60min

description

SillyTavern versions 1.12.13 through 1.19.0 accept request bodies before authentication and allowlist enforcement. A remote unauthenticated attacker can consume server memory and CPU and disrupt availability by submitting large or compressed requests, especially when the service is reachable over the network.

mitigation

Do not expose the service directly to untrusted networks; place it behind a reverse proxy or gateway that enforces strict request-size, decompression, rate, and connection limits before requests reach SillyTavern. Restrict access to trusted users and networks until an updated release is available.

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.
deterministic
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.58%46th percentile
agent run time
24m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-10 14: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

Check only, differential: the check fires on the vulnerable build and is silent on the patched one.

source signals

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

  1. 2026-10-10 14:15Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1171",
  "cve_id": "CVE-2026-108545",
  "display_id": "CVE-2026-108545",
  "ghsa_id": "GHSA-g54j-r2jq-rm6q",
  "euvd_id": "EUVD-2026-96340",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated request-body resource exhaustion in SillyTavern",
  "summary": "SillyTavern versions 1.12.13 through 1.19.0 accept request bodies before authentication and allowlist enforcement. A remote unauthenticated attacker can consume server memory and CPU and disrupt availability by submitting large or compressed requests, especially when the service is reachable over the network.",
  "mitigation": "Do not expose the service directly to untrusted networks; place it behind a reverse proxy or gateway that enforces strict request-size, decompression, rate, and connection limits before requests reach SillyTavern. Restrict access to trusted users and networks until an updated release is available.",
  "vendor": "SillyTavern",
  "product": "SillyTavern",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.12.13, <= 1.19.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "SillyTavern",
      "purl": null
    }
  ],
  "cwes": [
    400
  ],
  "cvss_score": 8.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.0058,
  "epss_percentile": 0.4653,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 24.244636983333333,
  "t0_at": "2026-10-10T14:15:52.273000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-10T15:41:18.205098+00:00",
      "days": 0.059327917800925924,
      "is_lower_bound": false,
      "measured_at": "2026-10-10T14:15:52.273000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-10T14:15:52.273000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-10T14:15:52.273000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-108545"
    }
  }
}

published 2026-10-10 15:17Z
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.