CVE-2026-104018

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

GHSA-fjrv-5j96-cvhx ↗EUVD-2026-90976 ↗

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.
Wind River Systems Inc VxWorks 7 VxWorks 7
fixed in 26.09
ETK-2026-272, permanent identifier
19d 17h 27msince last run
9mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h38m
0
+4h
+6h
+8h
+10h
+12h

description

VxWorks 7 releases before 26.09 are affected in deployments that enforce per-user command privileges. An authenticated user with restricted shell permissions may be able to run commands outside their assigned authorization, enabling privilege escalation.

mitigation

Upgrade VxWorks 7 to version 26.09. Until upgrading, restrict shell access to trusted administrators and limit use of accounts with command-shell access.

fixed in 26.09

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, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.64%49th percentile
agent run time
9m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-01 17:35Z
Δ 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 17:35Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-272",
  "cve_id": "CVE-2026-104018",
  "display_id": "CVE-2026-104018",
  "ghsa_id": "GHSA-fjrv-5j96-cvhx",
  "euvd_id": "EUVD-2026-90976",
  "status": "published",
  "anchor_state": "anchored",
  "title": "VxWorks 7 command shell privilege management flaw",
  "summary": "VxWorks 7 releases before 26.09 are affected in deployments that enforce per-user command privileges. An authenticated user with restricted shell permissions may be able to run commands outside their assigned authorization, enabling privilege escalation.",
  "mitigation": "Upgrade VxWorks 7 to version 26.09. Until upgrading, restrict shell access to trusted administrators and limit use of accounts with command-shell access.",
  "vendor": "Wind River Systems Inc",
  "product": "VxWorks 7",
  "affected": [
    {
      "affected_notes": [
        "VxWorks 7"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [
        "26.09"
      ],
      "package_name": "VxWorks 7",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0064,
  "epss_percentile": 0.4957,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 9.458851816666666,
  "t0_at": "2026-10-01T17:35:20.063000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-01T17:35:20.063000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-01T17:35:20.063000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-104018"
    }
  }
}

published 2026-10-01 19:03Z
last change 2026-10-21 09:43Z

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.