How severe is CVE-2025-70083?

CVE-2025-70083 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2025-70083 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (10th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-70083?

CVE-2025-70083 affects Opensatkit. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2025-70083?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2025-70083 have an EU (EUVD) identifier?

Yes. CVE-2025-70083 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-207394.

When was CVE-2025-70083 published?

CVE-2025-70083 was published on 2026-02-11 and last updated on 2026-06-17.

CVE-2025-70083

CVE-2025-70083 is a high-severity vulnerability in Opensatkit with a CVSS 3.x base score of 7.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-121.

Key facts

Severity: High (CVSS 3.x base score 7.8)
EPSS exploit prediction: 0% (10th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-207394
Weakness: CWE-121
Affected product: Opensatkit
Published: 2026-02-11
Last modified: 2026-06-17

Description

An issue was discovered in OpenSatKit 2.2.1. The DirName field in the telecommand is provided by the ground segment and must be treated as untrusted input. The program copies DirName into the local buffer DirWithSep using strcpy. The size of this buffer is OS_MAX_PATH_LEN. If the length of DirName is greater than or equal to OS_MAX_PATH_LEN, a stack buffer overflow occurs, overwriting adjacent stack memory. The path length check (FileUtil_AppendPathSep) is performed after the strcpy operation, meaning the validation occurs too late and cannot prevent the overflow.

Frequently asked questions

What is CVE-2025-70083?: An issue was discovered in OpenSatKit 2.2.1. The DirName field in the telecommand is provided by the ground segment and must be treated as untrusted input. The program copies DirName into the local buffer DirWithSep using strcpy. The size of this buffer is OS_MAX_PATH_LEN. If the length of DirName is greater than or equal to OS_MAX_PATH_LEN, a stack buffer overflow occurs, overwriting adjacent stack memory. The path length check (FileUtil_AppendPathSep) is performed after the strcpy operation, meaning the validation occurs too late and cannot prevent the overflow.
How severe is CVE-2025-70083?: CVE-2025-70083 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2025-70083 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (10th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-70083?: CVE-2025-70083 affects Opensatkit. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-70083?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-70083 have an EU (EUVD) identifier?: Yes. CVE-2025-70083 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-207394.
When was CVE-2025-70083 published?: CVE-2025-70083 was published on 2026-02-11 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:opensatkit:opensatkit:2.2.1:*:*:*:*:*:*:*

More vulnerabilities in Opensatkit

CVE-2025-70085 — Critical (CVSS 9.8): An issue was discovered in OpenSatKit 2.2.1. The EventErrStr buffer has a fixed size of 256 bytes. The code uses…
CVE-2025-70084 — High (CVSS 7.5): Directory traversal vulnerability in OpenSatKit 2.2.1 allows attackers to gain access to sensitive information or…

All CVEs affecting Opensatkit →

Other CWE-121 (Stack-based Buffer Overflow) vulnerabilities

CVE-2026-12848 — Critical (CVSS 10.0): GV-I/O Box 4E is a smart embedded device with 4 input and 4 relays output that can be controlled over Ethernet and…
CVE-2026-12847 — Critical (CVSS 10.0): GV-I/O Box 4E is a smart embedded device with 4 input and 4 relays output that can be controlled over Ethernet and…
CVE-2026-12846 — Critical (CVSS 10.0): GV-I/O Box 4E is a smart embedded device with 4 input and 4 relays output that can be controlled over Ethernet and…
CVE-2026-12485 — Critical (CVSS 10.0): GV-I/O Box 4E is a smart embedded device with 4 input and 4 relays output that can be controlled over Ethernet and…
CVE-2026-37541 — Critical (CVSS 10.0): Buffer overflow vulnerability in Open Vehicle Monitoring System 3 (OVMS3) 3.3.005. In canformat_gvret.cpp, the length…
CVE-2026-42996 — Critical (CVSS 10.0): JS8Call through 2.3.1 and JS8Call-improved before 3.0 have a stack-based buffer overflow via a radio transmission of…

Browse all CWE-121 (Stack-based Buffer Overflow) vulnerabilities →