ARISTA WI-FI ACCESS POINTS C-260 AND C-250 · CVE-2026-102166 · Infrastructure
NO FIX YET · SEE WHAT TO DO
Arista C-260 and C-250 wireless access points ship with the same cryptographic keys on every unit, used to verify firmware images and authenticate SSLP. An attacker who obtains those keys can build modified firmware that passes the device's verification checks.
first public Nov 10, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Any team running Arista C-260 or C-250 Wi-Fi access points, on any AP software release, is affected. The access points ship with the same static keys on every unit for firmware verification and SSLP authentication, so someone who obtains the keys can build firmware that passes the checks. Arista's CVSS vector is adjacent-network, so look at who can reach the AP management network. Teams without these two models, or with other Arista AP models, can skip it.
Not affected if eos-products, other-ap-models
Who cares access-points, arista, c-250, c-260, hardcoded-credentials, title-review, wireless
Arista C-260 and C-250 access points ship with fleet-wide static cryptographic keys used for firmware image verification and SSLP authentication. An attacker who is able to access these keys would be able to create modified firmware that will pass verification checks. This vulnerability is specific to the C-260 and C-250 models; other access point models enforce digitally signed upgrade images with secure boot and are not affected by this issue.
This page as .md · .json · CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.