The Kubernetes Security Response Committee is correcting inaccurate CVE records for several long-standing architectural vulnerabilities that lack code-based fixes. By reclassifying these as unfixed, the project aims to improve vulnerability scanner accuracy and ensure cluster administrators apply the necessary manual security mitigations.
Key points
Vulnerability records must accurately reflect architectural trade-offs that cannot be resolved via standard code patches.
Inaccurate 'fixed version' fields in CVE databases cause false negatives in automated scanning tools.
Architectural risks often require administrative configuration changes rather than binary updates.
Data integrity in security feeds is essential for accurate risk assessment and threat modeling.