Following a per-CVE deep link without JavaScript? Every advisory is published at its own address as a page, data/advisory-pages/<ID>.html (a new endpoint — a 404 means the published feed predates it), and as JSON at data/advisories/<ID>.json (upper-case the id); the full feed is at data/index.json. See llms.txt for the machine-readable contract.

Choose an advisory set. Each section tracks per-CVE fix status for a different class of AKS artifact.

VHD (node image) advisory

Per-CVE fix status for AKS node images — the Azure Linux & Ubuntu base packages baked into the VHD. Live search, installed-path lookup, and extended-binary coverage.

Open the VHD advisory →

Container image advisory

Per-CVE status for the container/OCI images AKS runs on your cluster — control plane, addons, CSI drivers, service mesh and Arc agents — keyed on your Kubernetes version. Bulk CVE paste, TSV/CSV export, and two evidence axes kept separate. Tracked in issue #40.

Open the container-image advisory →