CVE-2026-87550

Validating that output matches expected content directly mitigates failures to properly encode or escape data for its destination context.

A.8.25 mandates secure SDLC practices including secure coding guidelines, security requirements, checkpoints, testing (scans/penetration), and developer training that reach output encoding/escaping to stop injection-style exploits, but leaves a bounded remainder (e.g. ad-hoc/non-SDLC code changes, incomplete guideline enforcement, or non-software outputs)

Application security requirements include explicit rules for safe output handling and encoding.

A.8.27 mandates security-by-design principles (including distrust external input, secure session control, data validation/sanitization, defense-in-depth, and design reviews against attack patterns) that reach output encoding/escaping for many common channels, but leaves a bounded remainder (e.g. ad-hoc or non-reviewed custom protocols, unsafe string concatenation in obscure sinks, or cases where the principles are only documented and not enforced in implementation).

Secure coding standards explicitly require correct output encoding and escaping to preserve message structure.

Security testing can detect missing or incorrect encoding but does not itself implement the control.