dbcve.org
YamcsApplication · Spaceapplications

CVE-2026-44632

CRITICAL · 9.1 CVSS v3.1 Published 2026-07-16
Fix available
A fix is available. Upgrade to 5.12.7 or later.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable Zero-click 5 weeks old

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 · unedited
Yamcs is a mission control framework. Prior to 5.12.7, a server-side code injection vulnerability existed in the Yamcs algorithm evaluation engine org.yamcs.algorithms.JavaExprAlgorithmExecutionFactory, which dynamically compiled and evaluated user-controlled algorithm text through the Janino compiler without enforcing a secure sandbox, so an authenticated user with the ChangeMissionDatabase privilege could override an existing algorithm's text via the mission database REST API and inject Java code (for example using java.lang.Runtime) to achieve remote code execution on the underlying host operating system. This issue is fixed in versions 5.12.7 and 5.13.0, which disable algorithm editing by default.

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 · high confidence

Yamcs mission control framework versions prior to 5.12.7 contain a server-side code injection vulnerability in the JavaExprAlgorithmExecutionFactory class. The algorithm evaluation engine dynamically compiles user-controlled algorithm text through the Janino compiler without a secure sandbox, allowing authenticated users with ChangeMissionDatabase privilege to inject arbitrary Java code (e.g., java.lang.Runtime) via the mission database REST API for remote code execution.

MitigationUpgrade to Yamcs version 5.12.7 or 5.13.0, which disables algorithm editing by default. Until upgrade, restrict or revoke the ChangeMissionDatabase privilege from untrusted users.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
YamcsApplication
Affected:< 5.12.7

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Yamcs installation and version
    Locate the Yamcs installation directory and check the version file (typically version info in the startup scripts, WAR file, or pom.xml in the source). Compare the installed version to the affected range: versions < 5.12.7 are vulnerable.
    Affected if Installed version is lower than 5.12.7
  2. Verify algorithm execution engine is in use
    Check the Yamcs configuration (yamcs.yaml) for JavaExprAlgorithmExecutionFactory or algorithm-related settings. Inspect whether algorithms are defined in the mission database.
    Affected if JavaExprAlgorithmExecutionFactory is configured and algorithms are being evaluated
  3. Audit ChangeMissionDatabase privilege assignments
    Review user roles and permissions in Yamcs (via admin UI or user database). Identify which users or groups have the ChangeMissionDatabase privilege.
    Affected if Any user account with reduced trust or shared credentials has ChangeMissionDatabase privilege
  4. Confirm algorithm editing is permitted
    Check if the algorithm editor interface is accessible to non-admin users with ChangeMissionDatabase privilege. Verify no additional access controls restrict algorithm creation/modification.
    Affected if Authenticated users with ChangeMissionDatabase can access and modify algorithm definitions

A user is affected if Yamcs version is below 5.12.7 AND the JavaExprAlgorithmExecutionFactory is active AND untrusted users possess ChangeMissionDatabase privilege allowing algorithm code injection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 5.12.7 or later
Fixed in 5.12.7
Interim mitigation

Upgrade to Yamcs version 5.12.7 or 5.13.0, which disables algorithm editing by default. Until upgrade, restrict or revoke the ChangeMissionDatabase privilege from untrusted users.

Recommended fix High confidence

Upgrade to Yamcs 5.12.7 or 5.13.0

  1. Identify the current Yamcs version in use by checking the deployed artifacts or startup logs
  2. Review existing mission database algorithms for any suspicious modifications
  3. Upgrade Yamcs to version 5.12.7 or 5.13.0 following the standard upgrade procedure for your deployment method (e.g., Docker, JAR, or package manager)
  4. After upgrading, verify that algorithm editing is disabled by default as part of the security fix
  5. If algorithm editing is required, explicitly enable it through configuration after assessing the security implications
  6. Audit user accounts with ChangeMissionDatabase privilege to ensure only necessary users have this capability
Caveat Algorithm editing is now disabled by default, which may break existing workflows that rely on dynamic algorithm modification via the REST API

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Yamcs Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44632 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44632 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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