CVE-2026-78287

validatedZero produced an exploit or a check.
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.
Staggs <= 3.3.0
CWE-94 Improper Control of Generation of Code ('Code Injection')
ETK-2026-4161Zero's internal tracking ID, independent of the CVE number., permanent identifier
+19mTTV
<1mAI 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+19magent stopped
0
+5min
+10min
+15min

description

Staggs STAGGS versions through 3.3.0 are affected by a code-injection flaw that can enable remote code inclusion. A remote attacker may exploit the issue without authentication or user interaction where the affected plugin is reachable.

mitigation

Disable or remove the affected STAGGS plugin until a vendor-corrected release is available. Restrict public access to systems running it to reduce exposure.

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.
–
agent run time
<1m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-11 11:00Z
Δ 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

Upstream: a detection for this already ships elsewhere, so we didn't generate a new one. The credit goes to whoever did.

source signals

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

  1. 2026-11-11 11:00Z
    cve_org: trigger signal, started the run
  2. 2026-11-11 11:19Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4161",
  "cve_id": "CVE-2026-78287",
  "display_id": "CVE-2026-78287",
  "ghsa_id": null,
  "euvd_id": null,
  "status": "published",
  "anchor_state": "anchored",
  "title": "Remote code inclusion in Staggs STAGGS",
  "summary": "Staggs STAGGS versions through 3.3.0 are affected by a code-injection flaw that can enable remote code inclusion. A remote attacker may exploit the issue without authentication or user interaction where the affected plugin is reachable.",
  "mitigation": "Disable or remove the affected STAGGS plugin until a vendor-corrected release is available. Restrict public access to systems running it to reduce exposure.",
  "vendor": "Staggs",
  "product": "STAGGS",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 3.3.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "staggs",
      "purl": null
    }
  ],
  "cwes": [
    94
  ],
  "cvss_score": 10,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "upstream",
  "exploit": false,
  "pipeline_minutes": 0.0109105,
  "t0_at": "2026-11-11T11:00:22.307000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-11T11:19:50.093151+00:00",
      "days": 0.013516043414351852,
      "is_lower_bound": false,
      "measured_at": "2026-11-11T11:00:22.307000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-11-11T11:00:22.307000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-11T11:00:22.307000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-78287"
    }
  }
}

published 2026-11-11 11:19Z
last change 2026-11-11 11:19Z

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.