CVE-2026-80726 This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
Not scored
Published
Updated
Check this codebase for CVE-2026-80726 and fix it if it is affected.
What it is: CVE-2026-80726 is an use after free vulnerability, published on 3 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80726 in the wild and no public exploit code.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-80726/ (Markdown: https://insights.sbomify.com/CVE-2026-80726/index.md)
A use-after-free vulnerability in the Linux kernel's KVM MMU allows local attackers to potentially execute arbitrary code or escalate privileges.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-80726?
CVE-2026-80726 is an use after free vulnerability, published on 3 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
Which versions are affected by CVE-2026-80726?
How do I fix CVE-2026-80726?
Apply the vendor's patch.
Upgrade to the fixed version. These bugs are found with fuzzing and sanitisers and avoided by memory-safe languages. More about Use after free.
Is CVE-2026-80726 being exploited?
There is no known exploitation of CVE-2026-80726 in the wild and no public exploit code.
Sources
Also known as AZL-99062, BELL-CVE-2026-80726, DEBIAN-CVE-2026-80726, GHSA-j8gw-c9fh-xgv4, UBUNTU-CVE-2026-80726.