Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-c64q-hj4j-375f

Yamcs vulnerable to authenticated remote code execution via unescaped StreamSQL `LIKE` pattern compiled by Janino (`LikeExpression`)

CVSS 9.9 CriticalCriticalEPSS 0.0065 · 51st percentile

Critical, because:

  • CVSS score 9.9: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 28 Aug 2026, 17:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.yamcs:yamcs-coreMaven>=5.13.0, <5.13.2 || <5.12.85.13.2, 5.12.8
Identifiers
GHSA-c64q-hj4j-375f · CVE-2026-55565
Weakness (CWE)
CWE-94
Tags
Published
28 Aug 2026
Updated
28 Aug 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Yamcs (org.yamcs:yamcs-core) versions 5.13.0 up to but not including 5.13.2, and versions below 5.12.8, are vulnerable. An authenticated user with a read-only archive privilege, such as ReadEvents, ReadTables, or ReadActivities, can send a LIKE pattern containing a double quote to break out of the generated Java code. This allows arbitrary OS command execution as the user running Yamcs. Upgrade to 5.13.2 or 5.12.8, which contain fixes.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.9 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0065, the 51st percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:19 UTC First seen by agentprime
  2. 31 Oct 2026, 14:19 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.