Isovalent · Vulnerability Disclosure

Isovalent Vulnerability Disclosure

Vulnerability disclosure

Isovalent publishes a vulnerability disclosure policy for reporting security issues. A dedicated security contact is published.

CompanyNetworkingKuberneteseBPFSecurityObservabilityCloud NativeService MeshCNIContainer Networking
Program:

Disclosure Policy

Policy
https://github.com/cilium/cilium/security/policy
Policy
https://docs.cilium.io/en/latest/security/threat-model/

Security Contact

Contact
security@cilium.io

Source

Vulnerability Disclosure

Raw ↑ 
generated: '2026-07-19'
method: searched
probe: true
source: https://github.com/cilium/cilium/blob/main/SECURITY.md
policy:
- https://github.com/cilium/cilium/security/policy
- https://docs.cilium.io/en/latest/security/threat-model/
contact:
- security@cilium.io
advisories: https://github.com/cilium/cilium/security/advisories
cve: true
notes: >-
  Cilium (maintained by Isovalent) runs a private security mailing list disclosure
  process. Vulnerabilities are reported to security@cilium.io ahead of public
  disclosure and are handled by the Cilium Security Team, which publishes GitHub
  Security Advisories with associated CVE IDs and reporter credit. The Isovalent
  marketing domain returns a soft-404 SPA shell for /.well-known/security.txt and
  /vulnerability-disclosure/, so the verified disclosure surface is the Cilium
  project SECURITY.md and GitHub Security Advisories.
evidence:
- source: https://github.com/cilium/cilium/blob/main/SECURITY.md
  kind: security policy
  keywords:
  - security@cilium.io
  - private security mailing list
  - github security advisory
  - cve