CVE-2026-55511

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 50% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Yamcs is a mission control framework. Prior to 5.12.8 and 5.13.2, Yamcs allows a user with SystemPrivilege.ControlArchiving to create a double-quoted StreamSQL column name that is interpolated into generated Java source by Expression.fillCode_InputDefVars and Expression.sanitizeName. A sum aggregate reaches yamcs-core/src/main/java/org/yamcs/yarch/streamsql/CompilableAggregateExpression.java and yamcs-core/src/main/java/org/yamcs/yarch/streamsql/funct/SumExpression.java through SelectExpression.compile, where Janino SimpleCompiler.cook compiles the injected source. POST /api/archive/{instance}:executeSql can therefore execute arbitrary Java in the Yamcs server process, exposing mission data and credentials and permitting telemetry tampering or denial of service. This issue is fixed in versions 5.12.8 and 5.13.2.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
46(Track)
EG Risk 46/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
50%
KEV
Not listed

Published

August 28, 2026

Last Modified

August 28, 2026

Advisory Details (5)

Auto-updated Aug 28, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github Patch Available🟡 PoC Available

Authenticated RCE via StreamSQL aggregate-compiler column-name injection in Yamcs `executeSql` · Advisory · yamcs/yamcs · GitHub

https://github.com/yamcs/yamcs/security/advisories/GHSA-3g44-3m7x-cgg2
github_release Patch Available

Yamcs 5.13.2

Patch available: yamcs/yamcs yamcs-5.13.2

https://github.com/yamcs/yamcs/releases/tag/yamcs-5.13.2
github_release Patch Available

Yamcs 5.12.8

Patch available: yamcs/yamcs yamcs-5.12.8

https://github.com/yamcs/yamcs/releases/tag/yamcs-5.12.8
github_commit

commit b65a3d78178b (yamcs/yamcs)

Fix landed in yamcs/yamcs commit b65a3d78178b — awaiting tagged release

https://github.com/yamcs/yamcs/commit/b65a3d78178ba99a58b753feda6ecc3b5a694f13
github_commit

commit 8c1070b12c0a (yamcs/yamcs)

Fix landed in yamcs/yamcs commit 8c1070b12c0a — awaiting tagged release

https://github.com/yamcs/yamcs/commit/8c1070b12c0a6c003903325cb2a1013347e2dbde

Vendor Advisories for CVE-2026-55511(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 4× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:46 UTCEG score recompute
  2. 2026-08-30 01:22 UTCEPSS rescore
  3. 2026-08-28 20:25 UTCEG score recompute
  4. 2026-08-28 17:11 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-55511?
CVE-2026-55511 is a critical vulnerability published on August 28, 2026. Yamcs is a mission control framework. Prior to 5.12.8 and 5.13.2, Yamcs allows a user with SystemPrivilege.ControlArchiving to create a double-quoted StreamSQL column name that is interpolated into generated Java source by Expression.fillCode_InputDefVars and Expression.sanitizeName. A sum…
When was CVE-2026-55511 disclosed?
CVE-2026-55511 was first published in the National Vulnerability Database on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55511 actively exploited?
CVE-2026-55511 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 50.4% of all scored CVEs.
What is the CVSS score of CVE-2026-55511?
CVE-2026-55511 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-55511?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55511, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-55511

Explore →

Is Your Infrastructure Affected by CVE-2026-55511?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs