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 55548 yamcs insecure direct object reference idor in
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
Medium ยท CVSS 4.3CVE-2026-55548GHSA-8XJQ-PR36-CCGF

Yamcs: Insecure Direct Object Reference (IDOR) in PacketsApi allows unprivileged users to dump all telemetry packetsCVE-2026-55548

Answer in brief

CVE-2026-55548 records a Medium severity (CVSS 4.3) vulnerability in Yamcs: Insecure Direct Object Reference (IDOR) in PacketsApi allows unprivileged users to dump all telemetry packets. The current sources do not mark it as known exploited. The current feed maps org.yamcs:yamcs-core (maven), org.yamcs:yamcs-core (maven), org.yamcs:yamcs-core (maven), org.yamcs:yamcs-core (maven). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

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

Published Jul 16, 2026Updated Aug 28, 2026Source checked Oct 13, 2026First seen by HOL Jul 16, 2026Material review Aug 28, 2026
Upstream Advisory

Key facts

Risk
Medium ยท CVSS 4.3
Exploitation
Not marked as known exploited
Affected software
4 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 4.3. 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 org.yamcs:yamcs-core (maven), org.yamcs:yamcs-core (maven), org.yamcs:yamcs-core (maven), org.yamcs:yamcs-core (maven). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
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 org.yamcs:yamcs-core, 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

    Jul 16, 2026

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

    Aug 28, 2026

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

    Jul 16, 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
  • NVD vulnerability recordnvd.nist.gov
  • GitHub security advisorygithub.com
Upstream source description

## Summary The `PacketsApi.exportPackets` endpoint in Yamcs fails to properly enforce object-level privileges (`ReadPacket`) when an API request omits specific packet names. As a result, an attacker with a low-privileged account (or any authenticated user with zero privileges) can dump the entire archive of raw telemetry packets for a Yamcs instance. This leads to a massive Information Disclosure of sensitive mission telemetry, completely bypassing the intended Role-Based Access Control (RBAC) model. ## Vulnerability Details In `yamcs-core/src/main/java/org/yamcs/http/api/PacketsApi.java`, the `exportPackets` method processes requests to export raw packets from the `tm` (telemetry archive) table. ```java @Override public void exportPackets(Context ctx, ExportPacketsRequest request, Observer<HttpBody> observer) { String instance = InstancesApi.verifyInstance(request.getInstance()); Set<String> nameSet = new HashSet<>(request.getNameList()); ctx.checkObjectPrivileges(ObjectPrivilegeType.ReadPacket, nameSet); SqlBuilder sqlb = new SqlBuilder(XtceTmRecorder.TABLE_NAME); // ... time filters ... if (request.getNameCount() > 0) { sqlb.whereColIn("pname", nameSet); } String sql = sqlb.toString(); // ... ``` The method attempts to verify privileges using `ctx.checkObjectPrivileges(ObjectPrivilegeType.ReadPacket, nameSet)`. However, if the `request.getNameList()` is empty (i.e., the attacker does not specify any packet names to filter by), `nameSet` is empty. The `checkObjectPrivileges` method loops over this empty set and successfully passes without throwing a `ForbiddenException`. Since `request.getNameCount()` is 0, no `WHERE pname IN (...)` filter is added to the SQL query. The resulting `sql` query becomes a `SELECT * FROM tm` (with optional time filters). Finally, the query is executed and the results are streamed back to the user: ```java StreamFactory.stream(instance, sql, sqlb.getQueryArguments(), new StreamSubscriber() { @Override public void onTuple(Stream stream, Tuple tuple) { if (observer.isCancelled()) { stream.close(); return; } byte[] raw = (byte[]) tuple.getColumn(StandardTupleDefinitions.TM_PACKET_COLUMN); HttpBody body = HttpBody.newBuilder() .setData(ByteString.copyFrom(raw)) .build(); observer.next(body); } // ... ``` Crucially, unlike the `streamPackets` or `exportPacket` methods (which explicitly check `ctx.user.hasObjectPrivilege` for each packet retrieved before returning them), the `onTuple` handler in `exportPackets` **blindly streams all retrieved packets to the user without any per-row authorization checks**. Thus, a user who possesses no `ReadPacket` privileges at all can easily bypass authorization and extract all telemetry data from the archive. ## Steps to Reproduce 1. Start the Yamcs server (e.g., using the `simulation` example) with authentication enforced. 2. Log in as a low-privileged user (or use their credentials) who does **not** have the `ReadPacket` privilege. 3. Send an HTTP GET request to the export packets endpoint without specifying any `name` parameters: ```bash curl -v -u low_priv_user:password "http://localhost:8090/api/archive/simulator:exportPackets" -o dumped_packets.raw ``` 4. Observe that the server responds with HTTP `200 OK` and streams all raw packets to the response, saving them to `dumped_packets.raw`. 5. The downloaded file contains raw CCSDS Space Packets (binary telemetry data). 6. Contrast this with an attempt to fetch a specific packet (or calling `listPackets` for an unauthorized packet), which correctly enforces authorization and rejects the request. ## Impact Telemetry packets contain the core mission data, vehicle health status, and sensitive measurements (CCSDS Protocol data). This vulnerability completely breaks the access control model for telemetry data, allowing any authenticated user to exfiltrate all historical telemetry packets from the database. In an aerospace or mission-critical environment, this represents a severe data leak (Massive Information Disclosure) of proprietary or classified spacecraft data. ## Remediation Ensure that `exportPackets` enforces the same per-row privilege checks as `streamPackets`. Update the `onTuple` handler to check the user's privileges before emitting each packet: ```java @Override public void onTuple(Stream stream, Tuple tuple) { if (observer.isCancelled()) { stream.close(); return; } // FIX: Retrieve packet name and check authorization String pname = (String) tuple.getColumn(XtceTmRecorder.PNAME_COLUMN); if (ctx.user.hasObjectPrivilege(ObjectPrivilegeType.ReadPacket, pname)) { byte[] raw = (byte[]) tuple.getColumn(StandardTupleDefinitions.TM_PACKET_COLUMN); HttpBody body = HttpBody.newBuilder() .setData(ByteString.copyFrom(raw)) .build(); observer.next(body); } } ``` ## System Information - **Affected Versions:** 5.13.0 (Latest Release), 5.12.x, and current `master` branch. - **Tested Revision (master):** `309218c651680f79df11a8d0f8628f7033f98a83` - **Vulnerability Type:** Insecure Direct Object Reference (IDOR) / Logical Authorization Bypass ## PoC Images: - Check version: <img width="1157" height="489" alt="image" src="https://github.com/user-attachments/assets/58608222-b76f-4eb4-8e57-423523062992" /> - Check privilege of user: <img width="1439" height="953" alt="image" src="https://github.com/user-attachments/assets/aa7e55f2-2460-4f24-8b6f-d461d2499a6f" /> <img width="1214" height="224" alt="image" src="https://github.com/user-attachments/assets/e9123ae3-a194-462d-a5ca-2c0b1cc9cc6f" /> - Exploit: <img width="1728" height="685" alt="image" src="https://github.com/user-attachments/assets/0c7b3099-44d6-4392-bbaa-8e84cc151784" /> <img width="1768" height="797" alt="image" src="https://github.com/user-attachments/assets/df4016a5-d460-4611-a34a-8c0d206edd9c" />

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • SourceCodester Contact Tracing System Users.php move_uploaded_file unrestricted uploadAlso CWE-284
  • SourceCodester E-Learning System Users.php save_users unrestricted uploadAlso CWE-284
  • SourceCodester Library Management System add_admin.php move_uploaded_file unrestricted uploadAlso CWE-284
  • WordPress WPGraphQL plugin <= 2.23.1 - Sensitive Data Exposure vulnerabilityAlso CWE-862

Record context

Vulnerability class
Missing Auth
EPSS
Not reported
CWE IDs
CWE-284, CWE-862
Source
GitHub Security Advisories
Source checked
Oct 13, 2026
References
8 linked sources
Open source record