CVE-2026-41187 Tigera CVE debrief

Who should care

Users and administrators of Calico, especially those with multi-tiered policy configurations, should be aware of this vulnerability and take steps to mitigate it. They should verify their configurations to ensure proper authorization for tier-scoped policy resources and restrict deletecollection verb and wildcard verbs on tier-scoped policy resources to authorized users. Monitoring for and responding to potential bulk-deletion of policies in unauthorized tiers is also crucial. Calico users should review their current configurations and assess the potential impact of this vulnerability on their environments, considering the tier authorization boundary breach it allows. This includes evaluating the risk of bulk-deletion of policies across different tiers and implementing measures to prevent such unauthorized actions. Additionally, users should stay informed about any updates or patches released by Calico to address this vulnerability and plan for their timely implementation. Affected Calico deployments require immediate attention to prevent potential security breaches. Users should assign owners to follow up on mitigation efforts and ensure that proper authorization is in place for tier-scoped policy resources. This may involve reviewing and updating access controls, monitoring for suspicious activity, and preparing for potential incidents related to this vulnerability. By taking these steps, Calico users can reduce the risk associated with CVE-2026-41187 and protect their environments from potential attacks. Calico's apiserver vulnerability affects users with multi-tiered policy configurations, allowing bulk-deletion of policies across tiers they are not authorized for. Users should verify configurations, restrict verbs to authorized users, and monitor for bulk-deletions. The vulnerability breaches the tier authorization boundary, enabling users with deletecollection or wildcard verbs to delete policies in unauthorized tiers. Calico users must assess their environments, update configurations, and implement measures to prevent unauthorized actions. They should also stay informed about updates and patches from Calico and plan for their implementation. This includes

Technical summary

Calico's apiserver wraps tier-scoped resources through AuthorizeTierOperation but fails to invoke the Delete override on NetworkPolicy, GlobalNetworkPolicy, and their staged variants for DeleteCollection requests. This oversight enables users with the deletecollection verb or wildcard verbs on tier-scoped policy resources to bulk-delete policies across tiers they are not authorized for, effectively breaching the tier authorization boundary.

Defensive priority

Users of Calico should verify their configurations and ensure that proper authorization is in place for tier-scoped policy resources.

Recommended defensive actions

• Verify Calico configurations to ensure proper authorization for tier-scoped policy resources
• Restrict deletecollection verb and wildcard verbs on tier-scoped policy resources to authorized users
• Monitor for and respond to potential bulk-deletion of policies in unauthorized tiers
• Perform a thorough review of current configurations to identify potential security gaps
• Implement additional monitoring to detect suspicious bulk-deletion activities
• Conduct a vulnerability assessment to evaluate the risk of bulk-deletion of policies across different tiers
• Review and update access controls to prevent unauthorized actions related to tier-scoped policy resources

Evidence notes

The CVE-2026-41187 issue arises from Calico's apiserver not invoking the Delete override on NetworkPolicy, GlobalNetworkPolicy, and their staged variants for DeleteCollection requests. This allows users with the deletecollection verb or wildcard verbs on tier-scoped policy resources to bulk-delete policies in tiers they have no rights on, bypassing tier authorization.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.