# CVE-2025-64305: Columbia Weather Systems MicroServer Cleartext Storage in a File or on Disk

> Attackers can extract plaintext secrets from an SD card to modify firmware or gain admin access to the web portal.

- **Severity:** High 7.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jan 2026
- **Updated:** 7 Jan 2026
- **Also known as:** GHSA-9crg-j5q8-hwv3

## What is CVE-2025-64305?

CVE-2025-64305 is a high-severity vulnerability in Columbia Weather Systems MicroServer, published on 7 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

MicroServer copies parts of the system firmware to an unencrypted external SD card on boot, which contains user and vendor secrets. An attacker can utilize these plaintext secrets to modify the vendor firmware, or gain admin access to the web portal.

Weakness: CWE-313 (Cleartext Storage in a File or on Disk)

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


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

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

## Is CVE-2025-64305 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-64305 is a high-severity vulnerability in Columbia Weather Systems MicroServer, published on 7 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-64305 in the wild and no public exploit code.

Affected product: Columbia Weather Systems MicroServer. 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-64305/ (Markdown: https://insights.sbomify.com/CVE-2025-64305/index.md)
```

## Sources

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

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