CVE-2026-16521

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

GHSA-rwmh-x2cf-2ccg ↗EUVD-2026-110621 ↗

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.
SMCI MBD-X12STW-F 01.02.08
CWE-78 Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
ETK-2026-2737Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 59msince last run
1h 35mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h49m
0
+4h
+6h
+8h
+10h
+12h

description

The MBD-X12STW-F BMC syslog functionality is affected by an OS command injection flaw. An attacker able to provide input to the affected BMC function may cause commands to run when its related service is restarted.

mitigation

Restrict BMC management access to trusted administrators and isolated management networks, and avoid restarting the affected service after untrusted input. No fixed version is recorded; monitor vendor guidance for an update.

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
1h 35m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-27 07:22Z
Δ 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-27 07:22Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2737",
  "cve_id": "CVE-2026-16521",
  "display_id": "CVE-2026-16521",
  "ghsa_id": "GHSA-rwmh-x2cf-2ccg",
  "euvd_id": "EUVD-2026-110621",
  "status": "published",
  "anchor_state": "anchored",
  "title": "OS command injection in MBD-X12STW-F BMC syslog",
  "summary": "The MBD-X12STW-F BMC syslog functionality is affected by an OS command injection flaw. An attacker able to provide input to the affected BMC function may cause commands to run when its related service is restarted.",
  "mitigation": "Restrict BMC management access to trusted administrators and isolated management networks, and avoid restarting the affected service after untrusted input. No fixed version is recorded; monitor vendor guidance for an update.",
  "vendor": "SMCI",
  "product": "MBD-X12STW-F",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "01.02.08"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "MBD-X12STW-F",
      "purl": null
    }
  ],
  "cwes": [
    78
  ],
  "cvss_score": 7.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/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": 94.64723885,
  "t0_at": "2026-10-27T07:22:05.661000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-27T07:22:05.661000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-27T07:22:05.661000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-16521"
    }
  }
}

published 2026-10-27 07:36Z
last change 2026-10-27 11:00Z

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.