CVE-2026-75945 Race condition in EOS
Low 2.1
Published
Updated
Check this codebase for CVE-2026-75945 and fix it if it is affected.
What it is: CVE-2026-75945 is a low-severity vulnerability in Arista Networks EOS, published on 14 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-75945 in the wild and no public exploit code.
Affected product: Arista Networks EOS. No package-level version data is available, so check the vendor advisory linked from the reference page.
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-75945/ (Markdown: https://insights.sbomify.com/CVE-2026-75945/index.md)
A race condition allows a supplicant to remain authorized after a clear command, bypassing network access controls on Arista EOS devices.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-75945?
CVE-2026-75945 is a low-severity vulnerability in Arista Networks EOS, published on 14 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
A race condition may cause a supplicant to remain in an authorized state after a clear dot1x host all command is issued.
Weakness: CWE-459
Which versions are affected by CVE-2026-75945?
How do I fix CVE-2026-75945?
No fix has been published for CVE-2026-75945 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-75945 being exploited?
There is no known exploitation of CVE-2026-75945 in the wild and no public exploit code.
Sources
Also known as GHSA-5mw4-287j-72p2.