# CVE-2025-8286: Güralp Systems FMUS Series and MIN Series Devices

> Unauthenticated Telnet access allows attackers to modify configurations, manipulate data, or factory reset Güralp seismic monitoring devices.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jul 2025
- **Updated:** 15 Aug 2025
- **Also known as:** GHSA-5qv2-823h-cg9j

## What is CVE-2025-8286?

CVE-2025-8286 is a critical missing authorization vulnerability in Güralp FMUS Series, published on 31 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The affected products expose an unauthenticated Telnet-based command line interface that could allow an attacker to modify hardware configurations, manipulate data, or factory reset the device.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2025-8286 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8286 exists.

Public exploit code:

- Güralp Systems FMUS Series - Unauthenticated Access (nuclei)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-8286 is a critical missing authorization vulnerability in Güralp FMUS Series, published on 31 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8286 exists.

Affected product: Güralp FMUS Series. 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-8286/ (Markdown: https://insights.sbomify.com/CVE-2025-8286/index.md)
```

## Sources

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

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