Description
Yamcs is a mission control framework. Prior to 5.12.8 and 5.13.2, the PacketsApi.exportPackets endpoint in yamcs-core/src/main/java/org/yamcs/http/api/PacketsApi.java failed to enforce object-level ReadPacket privileges when a request omitted specific packet names: with an empty name list the ctx.checkObjectPrivileges(ObjectPrivilegeType.ReadPacket, nameSet) call passed over an empty set, no WHERE pname IN filter was applied to the resulting SELECT * FROM tm query, and the onTuple handler streamed every retrieved packet without any per-row authorization check, so a low-privileged or zero-privilege authenticated user could dump the entire raw telemetry packet archive and bypass the role-based access control model. This issue is fixed in versions 5.12.8 and 5.13.2, which enforce per-packet ReadPacket checks in exportPackets.
Published: 2026-07-16
Score: 4.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability is an insecure direct object reference in the PacketsApi.exportPackets endpoint, which allows a low‑privilege or zero‑privilege authenticated user to retrieve the entire telemetry packet archive. When the request omits the packet name list, the endpoint bypasses the per‑object ReadPacket permission checks, streams every packet returned by the database query, and provides full access to the raw data of potentially sensitive or mission‑critical telemetry information.

Affected Systems

The issue exists in Yamcs versions prior to 5.12.8 and 5.13.2. Users running yamcs 5.12.7 or earlier, or yamcs 5.13.1 or earlier, are susceptible; later releases have the per‑packet privilege checks in place.

Risk and Exploitability

The CVSS score of 4.3 indicates a moderate severity. An exploitation, and the vulnerability is not listed in the CISA KEV catalog, suggesting no widely known exploits yet. The EPSS score is less than 1%, indicating a low probability of exploitation in the wild. However, the attack requires only authenticated access with low privileges and relies on an API that is otherwise publicly documented, making it readily exploitable for an internal attacker or someone with legitimate user credentials but limited access rights. The lack of a filter on the database query means that once the endpoint is called, the attacker mission data.

Generated by OpenCVE AI on July 31, 2026 at 01:44 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Yamcs to version 5.12.8 or later, or to 5.13.2 or later, where the exportPackets endpoint enforces per‑packet ReadPacket checks.
  • If an immediate upgrade is not possible, restrict network or API gateway access to the exportPackets endpoint so that only users with privileged roles can invoke it.
  • Review and tighten the ReadPacket permission assignments so that only necessary roles retain this capability; remove the permission from low or anonymous user groups.

Generated by OpenCVE AI on July 31, 2026 at 01:44 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 16 Jul 2026 19:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Thu, 16 Jul 2026 17:45:00 +0000

Type Values Removed Values Added
First Time appeared Yamcs
Yamcs yamcs
Vendors & Products Yamcs
Yamcs yamcs

Thu, 16 Jul 2026 16:30:00 +0000

Type Values Removed Values Added
Description Yamcs is a mission control framework. Prior to 5.12.8 and 5.13.2, the PacketsApi.exportPackets endpoint in yamcs-core/src/main/java/org/yamcs/http/api/PacketsApi.java failed to enforce object-level ReadPacket privileges when a request omitted specific packet names: with an empty name list the ctx.checkObjectPrivileges(ObjectPrivilegeType.ReadPacket, nameSet) call passed over an empty set, no WHERE pname IN filter was applied to the resulting SELECT * FROM tm query, and the onTuple handler streamed every retrieved packet without any per-row authorization check, so a low-privileged or zero-privilege authenticated user could dump the entire raw telemetry packet archive and bypass the role-based access control model. This issue is fixed in versions 5.12.8 and 5.13.2, which enforce per-packet ReadPacket checks in exportPackets.
Title Yamcs: Insecure Direct Object Reference (IDOR) in PacketsApi allows unprivileged users to dump all telemetry packets
Weaknesses CWE-284
CWE-862
References
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-07-16T18:14:19.081Z

Reserved: 2026-06-16T23:01:04.075Z

Link: CVE-2026-55548

cve-icon Vulnrichment

Updated: 2026-07-16T18:13:06.465Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-07-31T01:45:06Z

Weaknesses