CVE-2026-67979
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIncorrect access control in the Executive Services dynamic application start path component of NASA cFS v7.0.1 allows attackers to execute arbitrary code via placing a shared object on target storage.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceIn NASA cFS v7.0.1, the Executive Services component's dynamic application start path lacks proper access controls, allowing attackers to place malicious shared objects (.so files) in a location where the application will load them, resulting in arbitrary code execution with the privileges of the loaded application.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify NASA cFS versionLocate the cFS installation directory and check version metadata files (such as version.h, cfs_version.h, or version.txt in the cfs root or build configuration). Alternatively, run 'grep -r "7.0.1" <cfs_install_path>' to find version strings.Affected if The installed version is exactly 7.0.1 or falls within the 7.0.x release family of the Executive Services component.
-
Confirm Executive Services is enabledLocate the Executive Services (exe) application configuration in the cFS mission directory. Check for the presence of an 'exe' table or configuration file (typically named exe_tbldef.sh, exe_msg.h, or similar) in the cFS build/output directory.Affected if The Executive Services dynamic application loader is present and configured in the cFS mission.
-
Inspect the dynamic application start pathExamine the Executive Services table definition or startup configuration file for the 'AppLoadPath' or 'StartPath' parameter. This defines where the cFS loads dynamic applications from at runtime.Affected if The start path points to a writable storage location (such as /cf, /tmp, or a user-writable directory) where untrusted files could be placed.
-
Verify storage location permissionsCheck file system permissions on the application start path directory. Use 'ls -la <start_path>' to list permissions. Verify if the directory allows write access by unauthorized users or processes.Affected if The directory specified in the dynamic application start path has weak permissions (world-writable, group-writable with broad group membership, or owned by a low-privilege user).
A system is affected if it runs NASA cFS v7.0.1 with Executive Services configured to load dynamic applications from a storage path with insufficient access controls, allowing untrusted users to place malicious .so files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict path validation and allowlisting for the dynamic application start path in Executive Services, ensuring only signed/verified executables from trusted paths can be loaded. Consider adding cryptographic verification of loaded objects.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-67979 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-67979 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data