← back to feed
ETK-2026-1734Zero's internal tracking ID, independent of the CVE number.

ETK-2026-1734Zero's internal tracking ID, independent of the CVE number.

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

GHSA-qjjw-3v66-279f ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
blakeblackshear/frigate >= 0.18.0, <= 0.18.1
fixed in >=0.18.2
CWE-184 Incomplete List of Disallowed Inputs
ETK-2026-1734Zero's internal tracking ID, independent of the CVE number., no cve assigned
cvss9.1cna vendorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
5d 18h 57msince last run
17mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
trigger signal −5.8dwaiting for further signals−5.8d
−4d
−2d
0

description

Frigate versions before 0.18.2 do not adequately restrict certain go2rtc stream sources. An authenticated administrator can use the bypass to cause commands to execute as root inside the Frigate container.

mitigation

Upgrade blakeblackshear/frigate to >=0.18.2 or later.

fixed in >=0.18.2

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, high privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
17m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ 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-15 22:40Z

this entry in the feed

GET /api/v1/feed/ETK-2026-1734

{
  "etk_id": "ETK-2026-1734",
  "cve_id": null,
  "display_id": "ETK-2026-1734",
  "ghsa_id": "GHSA-qjjw-3v66-279f",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Admin command execution in Frigate go2rtc stream handling",
  "summary": "Frigate versions before 0.18.2 do not adequately restrict certain go2rtc stream sources. An authenticated administrator can use the bypass to cause commands to execute as root inside the Frigate container.",
  "mitigation": "Upgrade blakeblackshear/frigate to >=0.18.2 or later.",
  "vendor": null,
  "product": "blakeblackshear/frigate",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.18.0, <= 0.18.1"
      ],
      "ecosystem": null,
      "fixed_versions": [
        ">=0.18.2"
      ],
      "package_name": "blakeblackshear/frigate",
      "purl": null
    }
  ],
  "cwes": [
    184
  ],
  "cvss_score": 9.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 17.149017566666668,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-15T22:40:50+00:00",
      "days": -5.803494857928241,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T17:57:51.979032+00:00",
      "url": "https://github.com/blakeblackshear/frigate/security/advisories/GHSA-qjjw-3v66-279f"
    }
  }
}

published 2026-10-15 23:41Z
last change 2026-10-21 17:47Z

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.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.