CVE-2026-116748

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

GHSA-jw4h-7968-5hj9 ↗EUVD-2026-110496 ↗

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.
transmission >= 4.0.0, < 4.1.3
fixed in 4.1.3
CWE-942 Permissive Cross-domain Security Policy with Untrusted Domains
ETK-2026-2699Zero's internal tracking ID, independent of the CVE number., permanent identifier
5h 32msince last run
16mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h50m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Transmission 4.0.0 through 4.1.2 permits untrusted web origins to obtain the RPC session token. A malicious web page visited by a user can then issue RPC requests that alter settings, run configured completion actions, or remove torrents and data.

mitigation

Upgrade Transmission to version 4.1.3 or later. Until upgraded, prevent users from visiting untrusted sites while they can access the Transmission RPC service.

fixed in 4.1.3

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
16m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-26 21:52Z
Δ 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-10-26 21:52Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2699",
  "cve_id": "CVE-2026-116748",
  "display_id": "CVE-2026-116748",
  "ghsa_id": "GHSA-jw4h-7968-5hj9",
  "euvd_id": "EUVD-2026-110496",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Permissive CORS in Transmission RPC server",
  "summary": "Transmission 4.0.0 through 4.1.2 permits untrusted web origins to obtain the RPC session token. A malicious web page visited by a user can then issue RPC requests that alter settings, run configured completion actions, or remove torrents and data.",
  "mitigation": "Upgrade Transmission to version 4.1.3 or later. Until upgraded, prevent users from visiting untrusted sites while they can access the Transmission RPC service.",
  "vendor": "transmission",
  "product": "transmission",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 4.0.0, < 4.1.3"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "4.1.3"
      ],
      "package_name": "transmission",
      "purl": null
    }
  ],
  "cwes": [
    942
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 15.6427714,
  "t0_at": "2026-10-26T21:52:45.799000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-26T21:52:45.799000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-26T21:52:45.799000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-116748"
    }
  }
}

published 2026-10-26 22:26Z
last change 2026-10-27 03:20Z

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.