How Automotive Teams Can Improve Software Visibility and Reduce Memory Safety Risk
Software-defined vehicles rely on complex software supply chains, long-lived embedded systems, and millions of lines of C and C++ code. As AI accelerates vulnerability discovery and exploit development, automotive teams need more than faster patching — they need stronger software visibility and built-in protection.
In this 2026 Auto-ISAC Virtual Partner Week session, Joe Saunders, Founder & CEO of RunSafe Security, explains how OEMs and suppliers can better understand what is inside their software, identify true software supply chain risk, and reduce the exploitability of memory safety vulnerabilities.
Joe discusses the limitations of binary-based SBOMs, the importance of build-time software bill of materials generation, and the need to trace software provenance across complex supplier ecosystems. He also explains how memory safety flaws such as buffer overflows, use-after-free errors, and heap corruption can put automotive platforms at risk — especially as vehicles are expected to remain supported for 20 to 25 years.
The session highlights how RunSafe Identify provides accurate build-time SBOM visibility and vulnerability insight, while RunSafe Protect helps harden software against memory-based exploitation at runtime.
Watch the session to learn how automotive software teams can move from reactive vulnerability management to proactive software resilience.
