CVE-2025-70085 Memory corruption in n/a

Critical 9.8 Published Updated

A stack buffer overflow in OpenSatKit allows attackers to execute arbitrary code or cause denial of service via crafted filenames.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2025-70085?

CVE-2025-70085 is a critical memory corruption vulnerability in n/a, published on 11 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

An issue was discovered in OpenSatKit 2.2.1. The EventErrStr buffer has a fixed size of 256 bytes. The code uses sprintf to format two filenames (Source1Filename and the string returned by FileUtil_FileStateStr) into this buffer without any length checking and without using bounded format specifiers such as %.*s. If the filename length approaches OS_MAX_PATH_LEN (commonly 64-256 bytes), the combined formatted string together with constant text can exceed 256 bytes, resulting in a stack buffer overflow. Such unsafe sprintf calls are scattered across multiple functions in file.c, including FILE_ConcatenateCmd() and ConcatenateFiles(), all of which fail to validate the output length.

Weakness: CWE-121

Which versions are affected by CVE-2025-70085?

It affects 1 product.

Products include Opensatkit Opensatkit.

How do I fix CVE-2025-70085?

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

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2025-70085 being exploited?

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

Sources

Also known as GHSA-hfmq-6wjv-c7r3.

Is CVE-2025-70085 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free