HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members

Guard product

  • Guard overviewLocal security and control for AI agents and the tools they use.
  • FeaturesRuntime protection, policy routing, review, and evidence.

Explore Guard

  • Product previewWalk through Guard surfaces in read-only demo mode.
  • ComparisonCompare Guard with native controls and AI security vendors.

AI tools

  • All AI toolsEvery supported AI tool and how Guard applies policy to it.
  • Codex
  • Claude Code
  • Cursor
  • Antigravity CLI
  • OpenCode
  • Hermes
  • OpenClaw
  • GitHub Copilot CLI
  • Antigravity
  • Kimi
  • Grok
  • Pi / Oh My Pi
  • Zcode

Extensions

  • All extensionsBrowse command and MCP coverage with owners and stated limits.
  • Command coverageShell command protection across clouds, databases, backups, and packages.
  • MCP server coverageSee how Guard maps risk state across MCP tools and servers.
  • Core safetyThe safety floor listings that ship with Guard.
  • Data and resilienceBackup and storage command protection.
  • Cloud and infrastructureAWS, Azure, GCP, Kubernetes, and more.

Security

  • AI security hubSecurity research, advisories, and agent safety coverage.
  • AI tool securitySecurity profiles for each supported coding agent.
  • Safe labsHands-on attack simulations with safe boundaries.
  • Redacted warningsReal blocked actions with sensitive details removed.
  • AdvisoriesCoordinated disclosure reports for AI tooling.
  • Active CVEsSearch active CVEs affecting AI tooling.

Learn

  • Security guidesPractical guides for securing AI agent workflows.
  • DocsInstall, configure, and operate Guard with confidence.
  • ResearchPublished security research, benchmarks, and methodology.

Community

  • ReleasesVersion history, shipped changes and upgrade notes.
  • ContributorsThe people and contributions behind HOL Guard.
  • AffiliatesShare Guard with your audience and earn from referrals.
  • SponsorKeep agent security open: sponsor a project, place a banner, or fund a security initiative.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 55511 yamcs authenticated rce via streamsql aggregate
HOL Guard

Public security guidance for teams protecting AI harnesses, MCP servers, skills, prompts, and local tool execution.

Install Guard

AI Security

  • Prompt injection
  • MCP security
  • OWASP MCP mapping
  • Supply chain

Resources

  • Trust packet
  • Harness setup
  • Redacted warnings
  • Safe labs

Product

  • Install Guard
  • Pricing
  • Open dashboard
Guard
  • Guard Overview
  • Releases
  • Contributors
  • Install Guard
  • Pricing
Docs
  • Documentation Index
  • Developer Hub
  • API Reference
  • Root OpenAPI
  • Registry OpenAPI
  • Run in Postman
  • Standards
  • Submit ERC-8004 Contract
  • Feature Your Agent
Best Plugins
  • Browse Plugins
  • Plugin Launches
  • Best Claude Plugins
  • Best Codex Plugins
  • Best Grok Plugins
  • Best Kimi Plugins
  • Best DeepSeek Plugins
  • Best Antigravity Plugins
  • Best MCP Servers
  • Best Cursor Plugins
  • Best OpenCode Plugins
Best Agents
  • Best ERC-8004 Agents
  • Best Virtuals Agents
  • Best MCP Servers
  • Best A2A Agents
  • Best x402 Payable
  • All Categories
Community
  • Telegram
  • X
More
  • About HOL
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright ยฉ 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
Critical ยท CVSS 9.1CVE-2026-55511GHSA-3G44-3M7X-CGG2

Yamcs: Authenticated RCE via StreamSQL aggregate-compiler column-name injection in Yamcs `executeSql`CVE-2026-55511

Answer in brief

CVE-2026-55511 records a Critical severity (CVSS 9.1) vulnerability in Yamcs: Authenticated RCE via StreamSQL aggregate-compiler column-name injection in Yamcs `executeSql`. The current sources do not mark it as known exploited. The current feed maps yamcs/yamcs (generic), org.yamcs:yamcs-core (maven), org.yamcs:yamcs-core (maven), org.yamcs:yamcs-core (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 28, 2026Updated Sep 8, 2026Source checked Oct 12, 2026First seen by HOL Aug 28, 2026Material review Sep 8, 2026
Upstream Advisory

Key facts

Risk
Critical ยท CVSS 9.1
Exploitation
Not marked as known exploited
Affected software
5 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 9.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps yamcs/yamcs (generic), org.yamcs:yamcs-core (maven), org.yamcs:yamcs-core (maven), org.yamcs:yamcs-core (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
yamcs/yamcsgeneric< 5.12.8 || >= 5.13.0, < 5.13.2Not reported
org.yamcs:yamcs-coremaven>=5.13.0,<=5.13.15.13.2
org.yamcs:yamcs-coremaven<=5.12.75.12.8
org.yamcs:yamcs-coremaven>=5.13.0 <5.13.25.13.2
org.yamcs:yamcs-coremaven>=0 <5.12.85.12.8

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for yamcs/yamcs, org.yamcs:yamcs-core, org.yamcs:yamcs-core.
  2. 2Review the reported fix. Update org.yamcs:yamcs-core to 5.13.2; org.yamcs:yamcs-core to 5.12.8; org.yamcs:yamcs-core to 5.13.2; org.yamcs:yamcs-core to 5.12.8 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Aug 28, 2026

    Evidence: source:cvelist:source_dates:source-dates:record
  2. Source modified

    Sep 8, 2026

    Evidence: source:cvelist:source_dates:source-dates:record
  3. First seen by HOL

    Aug 28, 2026

Sources and claim methodology

  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • Netcore NR268 DHCP dhcp_dynamicip_show.cgi eval cross site scriptingAlso CWE-94
  • Netcore NR268 DHCP Hostname filter_hosts_dump.cgi eval cross site scriptingAlso CWE-94
  • Edimax BR-6208AC formFilter cross site scriptingAlso CWE-94
  • Edimax BR-6208AC HTTP Blocking formUrlb cross site scriptingAlso CWE-94
  • Edimax BR-6208AC Port Forwarding formPortFw cross site scriptingAlso CWE-94
  • IBM Maximo Application Suite - Location Service for Esri Component Code ExecutionAlso CWE-94

Record context

Vulnerability class
RCE
EPSS
Not reported
CWE IDs
CWE-94
Source
CVE List V5
Source checked
Oct 12, 2026
References
7 linked sources
Open source record