Security News

C++26 Hits a Snag as Experts Clash Over a Security-Focused Feature

The Register · 13 Nov 2026
Key Takeaway If your business relies on software written in C++, ask your vendors how they manage code safety and keep their products patched, because language-level safety features may not arrive on a predictable schedule.

The next version of the C++ programming language, known as C++26, may be delayed at the last minute. The cause is a disagreement over Contracts, a feature intended to improve security by helping developers catch programming errors that could otherwise lead to undefined behaviour. Contracts let developers add conditions and checks to their code, such as preconditions, postconditions and assertions.

In October, the draft standard failed its ISO ballot. There were 13 votes in favour, 9 against and 12 abstentions, which missed the requirement of no more than 25 percent negative votes. Contracts was the major sticking point for those who voted no.

The technical maintainers are deeply split. C++ creator Bjarne Stroustrup opposes the feature in its current form. He and his colleagues wrote that the proposal could add complexity and bloat, is not sufficiently tested, and could be done more effectively as a library. Others want Contracts included. Andreas Fertig, a member of the standardisation committee, believes the criticisms have already been examined and that blocking the proposal this late harms C++ itself. Contracts were also removed from C++20 over concerns about dangerous defaults. This article covers only the opening of the original report, so further developments are not included here.

C++ secure coding software development standards

Summarised by CISO AI from The Register, written with Claude Sonnet 5.5. We link back to every original so you can read it yourself.