# CVE-2026-120975: Security Advisory 0205


- **Severity:** Low 2.0 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:P/VC:N/VI:L/VA:L/SC:N/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** GHSA-3gjf-hwwx-cpxh

## What is CVE-2026-120975?

CVE-2026-120975 is a low-severity vulnerability in Arista Networks EOS, published on 10 Nov 2026. 

### Official description

On affected platforms running Arista EOS with automatic certificate management configured and automatic Certificate Authority (CA) certificate retrieval enabled, a malicious packet may cause the AutoCertMgmt process to be terminated unexpectedly. Managed X.509 certificates will not be renewed automatically and may eventually expire, potentially disrupting TLS-dependent services.

Weakness: CWE-197 (Numeric Truncation Error)

## Which versions are affected by CVE-2026-120975?


## How do I fix CVE-2026-120975?

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

## Is CVE-2026-120975 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120975 and fix it if it is affected.

What it is: CVE-2026-120975 is a low-severity vulnerability in Arista Networks EOS, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120975 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-120975/ (Markdown: https://insights.sbomify.com/CVE-2026-120975/index.md)
```

## Sources

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

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