Why CHERI
Vulnerabilities in everyday technology
Routers, vehicles, medical devices, appliances, phones and public services all run complex software, often including native code and reused libraries.
Why it matters
The human impact depends on the product and the authority of the vulnerable component, not only the technical bug class.
In brief
Routers, vehicles, medical devices, appliances, phones and public services all run complex software, often including native code and reused libraries. A memory-safety vulnerability in an exposed component can affect privacy, availability, safety or long-term support.
Key considerations
1. Connected devices
Untrusted network data reaches long-lived software that may be difficult to update.
2. Mixed-criticality products
Infotainment, communications or third-party code can sit near functions with higher consequence.
3. Essential services
A fault or compromise can disrupt operations and create recovery work across dependent organisations.
Evidence and caveats
Do not label a public incident as memory-safety-related without primary technical evidence. Examples should name the affected component and uncertainty.
Use evidence from a named system or source and keep claims proportionate. CHERI is one layer in a broader secure-design strategy.