# CVE-2025-6188: Security feature bypass in EOS

> Attackers can bypass security controls by sending malicious UDP packets with source port 3503, causing unexpected behavior in unauthenticated services.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2025
- **Updated:** 27 Aug 2025
- **Also known as:** GHSA-hjjq-j76f-mvq4

## What is CVE-2025-6188?

CVE-2025-6188 is a high-severity vulnerability in Arista Networks EOS, published on 25 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

On affected platforms running Arista EOS, maliciously formed UDP packets with source port 3503 may be accepted by EOS. UDP Port 3503 is associated with LspPing Echo Reply. This can result in unexpected behaviors, especially for UDP based services that do not perform some form of authentication.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

## Which versions are affected by CVE-2025-6188?


## How do I fix CVE-2025-6188?

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

## Is CVE-2025-6188 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-6188 and fix it if it is affected.

What it is: CVE-2025-6188 is a high-severity vulnerability in Arista Networks EOS, published on 25 Aug 2025. 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-2025-6188 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-2025-6188/ (Markdown: https://insights.sbomify.com/CVE-2025-6188/index.md)
```

## Sources

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

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