CVE-2025-64305VulnerabilityPublished 7 Jan 2026

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

Affects Columbia Weather Systems MicroServerSource CVE Database V5

Not known to be exploited · CVSS 7.1 High : upgrade to MS_4.1_14142 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

7.1High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in MS_4.1_14142

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

Attack Vector: Adjacent
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable system is bound to a protocol stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared proximity (e.g., Bluetooth, NFC, or IEEE 802.11) or logical network (e.g., local IP subnet), or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN within an administrative network zone).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 7 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Columbia Weather Systems MicroServer to MS_4.1_14142.

Affected software

Product	Affected	Fixed in
Columbia Weather SystemsMicroServer	Affected =0	Fixed in MS_4.1_14142

AI-suggested

European organizations should immediately implement strict physical security controls to prevent unauthorized access to MicroServer devices and their SD cards. Network segmentation should be enforced to limit access to the MicroServer’s network segment, reducing the risk of remote exploitation. Continuous monitoring and logging of device access and SD card usage can help detect suspicious activities early. Organizations should disable or restrict external SD card usage if possible or replace devices with more secure alternatives. If you cannot patch yet, consider deploying compensating controls such as encrypted tunnels for web portal access and multi-factor authentication to reduce the risk of unauthorized administrative access. Engage with Columbia Weather Systems to demand firmware updates that encrypt sensitive data on external storage and implement firmware integrity verification mechanisms. Regular security audits and penetration testing focusing on physical and network access to these devices will also help identify and mitigate risks. Finally, maintain an incident response plan tailored to potential firmware compromise scenarios.

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.

Impact

For European organizations, this vulnerability can lead to unauthorized access to critical weather monitoring systems, potentially disrupting data integrity and operational reliability. Compromised firmware could allow attackers to manipulate sensor data or device behavior, impacting decision-making in sectors such as agriculture, energy, transportation, and emergency services. The exposure of vendor secrets also risks supply chain security and could facilitate further attacks on related infrastructure. Given the reliance on accurate environmental data for regulatory compliance and safety, exploitation could have cascading effects on public safety and economic activities. The lack of encryption on removable media increases the risk of insider threats or physical tampering, especially in facilities with less stringent physical security. The vulnerability’s ease of exploitation without authentication raises the threat level for organizations with exposed or poorly segmented networks. Overall, the impact includes loss of confidentiality, integrity, and potential operational disruption, which are critical for European entities managing environmental and industrial systems.

CWE-313Cleartext Storage in a File or on Disk (opens in a new tab)
Variant weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product stores sensitive information in cleartext in a file, or on disk.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.6 (opens in a new tab)
V8.2.3 (opens in a new tab)
V8.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Jan 2026, 20:32 UTC

WeaknessesCWE-313

Technical details

References

Community reviews

Related threats