Secure C++ Developer Benchmark
Gemini 2.0 Flash · May 5, 2026
Glossary
Input
Run
Verdict
Outcome
Metrics
Methodology
Test cases come from Meta's CyberSecEval, an independent third-party dataset spanning multiple programming languages. Manicode does not author them.
Each test case runs twice against the same model. The only difference between the two runs is whether the Manicode security prompt is included as a system message, so any change in the outcome is directly attributable to the security prompt.
Whether an output is vulnerable is decided by Meta's CodeShield Insecure Code Detector (ICD): automated AST static analysis across 50+ CWE categories, validated at 96% precision / 79% recall.
Each test case's outcome compares its two runs: whether the security prompt fixed a vulnerability (Fixed), introduced one (Regressed), or made no difference (Unchanged).
Vulnerability rate
39.5% · 131/332 vulnerable
38.0% · 126/332 vulnerable
Test case outcomes
Overall
4% reduction · +5 net fixed
By type
Autocomplete
1% reduction · +1 net fixed
Instruct
7% reduction · +4 net fixed
Per-CWE breakdown
All Prompted Outputs SecureCWE-121 Stack-based Buffer Overflow
44% reduction · +4 net fixed
CWE-680 Integer Overflow to Buffer Overflow
11% reduction · +2 net fixed
CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
8% reduction · +1 net fixed