Critical Compilation Strictness for Certified Selective Hardening Against Compiler-Conditioned DNN Backdoors

Summary

This research defines critical compilation strictness, the smallest set of enforceable source and reference-semantic sites whose protection excludes a prescribed decision violation across all legal joint compiler configurations on a declared input domain. On a five-site ConvNet under PyTorch 2.6.0+cpu with the Inductor backend, the triggered target-label proportion rises from 0.1078 under eager execution to 0.9996 under compilation, and protecting only the feature stem is the unique minimum decision-preserving policy. The authors report that selective strictness reduces warmed batch latency by roughly 29% relative to all-strict execution.

Mitigation

The source discusses selective strictness as a protection policy: protecting only the minimal set of sites, such as the feature stem in the ConvNet case, preserves the decision. It does not describe a specific patch, fixed version, or configuration change for end users.

Related items

• MediumCVE-2026-113459: TYPO3 OpenAI API key exposed to backend users in page sourceSimilar attack · NVD/CVE Database
• HighCVE-2026-77926: Aix-DB remote code execution through ChatBI common agent execute toolSimilar attack · NVD/CVE Database
• CriticalCVE-2026-75128: Langchain-Chatchat unauthenticated shell command executionSimilar attack · NVD/CVE Database
• HighCVE-2026-109443: JoySafeter remote code execution via unsandboxed execute tool in CopilotSimilar attack · NVD/CVE Database
• HighCVE-2026-107366: IBM Langflow OSS message endpoints lack ownership verificationSimilar attack · NVD/CVE Database