CVE-2026-26309: Sprintf Null Byte Overwrite Oob
Writing to a string or array index immediately after `sprintf` without a bounds check can cause an out-of-bounds write. `sprintf` automatically writes a trailing null byte. Manually overwriting it after incrementing the position can corrupt the null-termination of dynamic strings (like `std::string`) if the new position aligns exactly with the end of the all
C++greprules fetch cve-2026-26309-sprintf-null-byte-overwrite-oob --engine opengrepDescription
Writing to a string or array index immediately after `sprintf` without a bounds check can cause an out-of-bounds write. `sprintf` automatically writes a trailing null byte. Manually overwriting it after incrementing the position can corrupt the null-termination of dynamic strings (like `std::string`) if the new position aligns exactly with the end of the all
Community feedback
0 rule-level signals from signed-in users.
- Useful reports
- 0
- Context false positives
- 0
- Metadata suggestions
- 0
Contextual precision
Aggregated from approved scan feedback. False-positive reports describe observed scan contexts, not a global rule verdict.
- Findings observed
- 0
- Projects
- 0
- Reporters
- 0
Precision details are collecting more signed-in reports before verdict counts or ratios are emphasized.
No approved finding verdicts yet.
No scan diagnostics reported yet.