JTC 1/SC 22/WG 23 C++ Vulnerability Discussions WG 23 N1560 April 27 2026 Participants Stephen Michell - convenor, SCC Peter Sommerlad - Switzerland Erhard Ploedereder - liaison Regrets Matt Butler - USA Loic Joly - AFNOR Richard Corden - Spain Paul Preney - Canada Actions: Issues addressed: Added new issues #222 Add Namespace concept to clause 4 #223 Add overload resolution concept to clause 4 Clauses addressed: 6.47 Inter language calling - improved clarity 6.48 Dynamically-linked code and self-modifying code fixed wording and references 6.49 Library Signature fixed wording and references 6.50 Unanticipated exceptions from library routines fixed wording and references 6.52 Suppression of language-defined runtime checking f fixed wording and references 6.53 Provision of inherently unsafe operations fixed wording and references 6.54 Obscure language features fixed wording and references 6.55 Unspecified behaviour fixed wording and references 6.56 Undefined behaviour fixed wording and references 6.57 Implementation-defined behaviour fixed wording and references 6.58 Deprecated language issues fixed wording and references 6.65 Modifying constants fixed wording All work is done on GitHub in the folder for ISO-IEC-JTC1-SC22-WG23-CPP. Please contact stephen.michell@maurya.on.ca for access. FROM THE CHAT 2026-04-27: 2026-04-27 10:28:45 From Peter Sommerlad to Everyone: This situation can be detected when the return type of `operator<=>` for a floating point type is `std::partial_ordering`. 2026-04-27 10:45:01 From Peter Sommerlad to Everyone: If parts of a system written in C++ are accessed through a `extern "C"` linkage interface, it is implementation defined, if a C++ exception from the library part can be caught on the other side of the interface. This situation can be avoided, by using a different error reporting mechanism for library exceptions across the C-linkage interface. 2026-04-27 10:53:23 From Peter Sommerlad to Everyone: Prevent throwing exceptions from a C++ library across extern "C" linkage.