Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Tue, 17 Feb 2026 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:opensatkit:opensatkit:2.2.1:*:*:*:*:*:*:* |
Thu, 12 Feb 2026 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-121 | |
| Metrics |
cvssV3_1
|
Thu, 12 Feb 2026 11:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Opensatkit
Opensatkit opensatkit |
|
| Vendors & Products |
Opensatkit
Opensatkit opensatkit |
Wed, 11 Feb 2026 18:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| References |
|
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2026-02-12T15:02:00.414Z
Reserved: 2026-01-09T00:00:00.000Z
Link: CVE-2025-70085
Updated: 2026-02-12T15:01:55.403Z
Status : Analyzed
Published: 2026-02-11T18:16:06.600
Modified: 2026-02-17T15:02:22.943
Link: CVE-2025-70085
No data.
OpenCVE Enrichment
Updated: 2026-02-12T11:19:23Z