# CVE-2020-26569: Other in n/a

> Malformed packets in EVPN VxLAN setups cause incorrect MAC-to-IP bindings, leading to cross-VLAN traffic leakage and potential data exposure or service disruption.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-77mv-h93c-9885

## What is CVE-2020-26569?

CVE-2020-26569 is a medium-severity vulnerability in n/a, published on 28 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In EVPN VxLAN setups in Arista EOS, specific malformed packets can lead to incorrect MAC to IP bindings and as a result packets can be incorrectly forwarded across VLAN boundaries. This can result in traffic being discarded on the receiving VLAN. This affects versions: 4.21.12M and below releases in the 4.21.x train; 4.22.7M and below releases in the 4.22.x train; 4.23.5M and below releases in the 4.23.x train; 4.24.2F and below releases in the 4.24.x train.

## Which versions are affected by CVE-2020-26569?

It affects 1 product.


Products: Arista Eos.

## How do I fix CVE-2020-26569?

No fix has been published for CVE-2020-26569 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-26569 being exploited?

There is no known exploitation of CVE-2020-26569 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2026-7473](https://insights.sbomify.com/CVE-2026-7473/): Arista Extensible Operating System Incomplete Comparison with Missing Factors (medium 6.9, exploited in the wild)
- [CVE-2015-8236](https://insights.sbomify.com/CVE-2015-8236/): Privilege escalation in n/a (critical 10.0)
- [CVE-2020-10188](https://insights.sbomify.com/CVE-2020-10188/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-18017](https://insights.sbomify.com/CVE-2017-18017/): Use after free in n/a (critical 9.8)
- [CVE-2017-14491](https://insights.sbomify.com/CVE-2017-14491/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-26569 and fix it if it is affected.

What it is: CVE-2020-26569 is a medium-severity vulnerability in n/a, published on 28 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-26569 in the wild and no public exploit code.

Affected product: n/a. 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-2020-26569/ (Markdown: https://insights.sbomify.com/CVE-2020-26569/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-26569
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-26569
- OSV: https://osv.dev/vulnerability/CVE-2020-26569

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-26569/
Summaries are generated and may contain mistakes; the official description above is the record.