Hello Gomolemo,
The reason you still see those vulnerabilities in the AKS report is because Defender for Cloud evaluates vulnerabilities based on the exact image digest that is currently running in your AKS cluster, not the tag. Even if you pushed a fixed image, if the cluster is still running pods based on the old digest, Defender will continue to report the old vulnerabilities.
Another point to note is that Defender does not update immediately. The registry scan and AKS cluster inventory refresh run on scheduled intervals. Until both have refreshed, the report may continue to show the older vulnerability state.
Also, if the old vulnerable image still exists in the container registry, Defender will list it in the report even if it is no longer deployed.
Once the patched digest is actually deployed in AKS, the old image is removed from the registry, and Defender completes its next scan cycle, the vulnerabilities will no longer appear in the report.
For your reference
https://docs.azure.cn/en-us/defender-for-cloud/view-and-remediate-vulnerabilities-for-images