CVE-2026-18449

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

GHSA-h8gp-mmvv-4j3c ↗EUVD-2026-110623 ↗

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 X12SPI 01.07.20
CWE-798 Use of Hard-coded Credentials
ETK-2026-2739Zero's internal tracking ID, independent of the CVE number., permanent identifier
51msince last run
24mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+3h36m
0
+2h
+6h
+8h
+10h
+12h

description

SMCI X12SPI BMC IPMI is affected by inadequate enforcement of message protection requirements. An unauthenticated network attacker may be able to execute commands by targeting an active IPMI session.

mitigation

Restrict IPMI access to a dedicated, trusted management network and block it from untrusted networks. Monitor for and apply vendor BMC firmware updates when a corrected release becomes available.

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-2739",
  "cve_id": "CVE-2026-18449",
  "display_id": "CVE-2026-18449",
  "ghsa_id": "GHSA-h8gp-mmvv-4j3c",
  "euvd_id": "EUVD-2026-110623",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper IPMI integrity enforcement in SMCI X12SPI",
  "summary": "SMCI X12SPI BMC IPMI is affected by inadequate enforcement of message protection requirements. An unauthenticated network attacker may be able to execute commands by targeting an active IPMI session.",
  "mitigation": "Restrict IPMI access to a dedicated, trusted management network and block it from untrusted networks. Monitor for and apply vendor BMC firmware updates when a corrected release becomes available.",
  "vendor": "SMCI",
  "product": "X12SPI",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "01.07.20"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "X12SPI",
      "purl": null
    }
  ],
  "cwes": [
    798
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 24.387635483333334,
  "t0_at": "2026-10-27T07:32:36.594000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-27T07:32:36.594000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-27T07:32:36.594000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-18449"
    }
  }
}

published 2026-10-27 08:06Z
last change 2026-10-27 11:35Z

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.