Quick answers
- Is CVE-2026-67979 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-67979 being exploited in the wild.
- How severe is CVE-2026-67979?
- Critical severity, with a CVSS score of 9.1, published 4 August 2026.
- Which products and versions are affected?
- Nasa cFS (core Flight System) v7.0.1.
- Is there a fix for CVE-2026-67979?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-67979 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-67979?
- Check whether you run Nasa cFS (core Flight System) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an insufficient access control flaw in the Executive Services (ES) dynamic application startup component. An attacker can leverage the CFDP (CCSDS File Delivery Protocol) file ingress path to place a malicious shared object (.so file) into a writable directory (/cf), and then use the CFE_ES_START_APP_CC command to load and execute that module with no integrity verification. The attack requires network access to the UDP command interface and the ability to send CFDP packets; if the cFS process runs as root (common in sample deployments), the injected code executes with root privileges. The root cause is the lack of validation between untrusted file storage paths and executable module loading, creating a direct privilege escalation vector. Patches are available through NASA cFS project updates that implement stricter controls.
Affected products
- NASA cFS (core Flight System) v7.0.1
Timeline
- 2026-06-28: disclosed
- 2026-08-04: advisory