CVE-2026-7406 is an untrusted pointer dereference in Autodesk's BMP parser. The parser accepts offset or pointer values embedded in the BMP file header or pixel data—specifically DIB header fields that encode offsets into the file buffer—and dereferences them without bounds validation. This creates a direct arbitrary read/write primitive. The vulnerability lives in bmpendian.c and related DIB functions that historically load directly into the core acad.exe address space rather than a sandboxed subprocess.
This is not a new vulnerability class. It's the fourth generation of the same root precondition in graphics-adjacent software: untrusted file data being parsed in an address space where computed pointers are treated as dereferenceable. The first generation (integer overflows in offset arithmetic) was patched with bounds checks. The second generation (bounds checks bypassed by fuzzing) was addressed with ASAN/UBSan. The third generation (semantic-gap exploits where the pointer is technically within bounds but violates parser assumptions about structure layout) exposed UBSan's gaps—it catches overflows, not type confusion. CVE-2026-7406 is the fourth generation, and it bypassed the same sanitizers for the same reason.
The immediate defensive actions: First, verify whether bmpendian.c and DIB functions compile with ASAN/MSAN and UBSan flags in your release builds. If they don't, treat adding them as a P0 infrastructure task—this vulnerability class is precisely what these sanitizers target. Second, determine whether the BMP handler runs in acad.exe's main address space or a sandboxed renderer process. If it's in-process, the untrusted pointer dereference is a direct primitive against core application memory. Third, the durable architectural fix is process-level file format handlers: extract the BMP decoder into a tightly constrained DLL with structured exception handling, a custom heap allocator, and read-only file access. This constrains the dereference target to a managed memory pool rather than raw pointers into the DIB buffer—even if the handler runs in-process, the arbitrary read/write primitive collapses to a bounded read within allocated bitmap data.
Note that the CVE description lacks specific version boundaries or patch details. The relevant check is whether your AutoCAD installation has received the 2026 security update. More broadly, this vulnerability is evidence that the defense-in-depth model fails at the file import boundary for untrusted formats. Adding a sandboxed rendering subprocess for untrusted file types would neutralize this entire attack class, not just this specific instance.