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

Published Jul 16, 2026
·
Updated

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.TABLENAME); // ... 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.TMPACKETCOLUMN); 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 lowprivuser:password "http://localhost:8090/api/archive/simulator:exportPackets" -o dumpedpackets.raw 4. Observe that the server responds with HTTP 200 OK and streams all raw packets to the response, saving them to dumpedpackets.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.PNAMECOLUMN); if (ctx.user.hasObjectPrivilege(ObjectPrivilegeType.ReadPacket, pname)) { byte[] raw = (byte[]) tuple.getColumn(StandardTupleDefinitions.TMPACKETCOLUMN); 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" />

Other sources

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.

MITRE

Affected Software

5 affected componentsFixes available
Yamcs yamcs-core>=0<5.12.8, >5.12.8<=5.13.2
Spaceapplications Yamcs<5.12.8
Spaceapplications Yamcs>=5.13.0<5.13.2
maven/org.yamcs:yamcs-core<=5.12.7
5.12.8
maven/org.yamcs:yamcs-core>=5.13.0<=5.13.1
5.13.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/org.yamcs:yamcs-core to a version that resolves this vulnerability.

    Fixed in 5.12.8
  2. Upgrade

    Upgrade maven/org.yamcs:yamcs-core to a version that resolves this vulnerability.

    Fixed in 5.13.2
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 5.12.8
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 5.13.2
  5. Configuration

    Update the exportPackets onTuple handler so it performs per-row object-level ReadPacket authorization checks before streaming/emitting each retrieved raw telemetry packet (matching the behavior of streamPackets/exportPacket).

    Yamcs PacketsApi (yamcs-core/src/main/java/org/yamcs/http/api/PacketsApi.java) - exportPackets onTuple privilege enforcement for ReadPacket = Add per-packet ctx.checkObjectPrivileges(ObjectPrivilegeType.ReadPacket, nameSet) / verify ctx.user.hasObjectPrivilege(ObjectPrivilegeType.ReadPacket, pname) before emitting each packet

Event History

Jul 16, 2026
CVE Published
via MITRE·04:09 PM
Data Sourced
via MITRE·04:09 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Aug 28, 2026
Advisory Published
via GitHub·05:15 PM
Data Sourced
via GitHub·05:15 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-55548?

CVE-2026-55548 has a medium severity rating of 4.3.

2

How do I fix CVE-2026-55548?

To fix CVE-2026-55548, upgrade to Yamcs version 5.12.8, 5.13.2 or newer.

3

What is the risk associated with CVE-2026-55548?

The risk associated with CVE-2026-55548 is rated at 22, indicating a significant potential for abuse.

4

What does CVE-2026-55548 exploit?

CVE-2026-55548 exploits an insecure direct object reference in the PacketsApi that allows unprivileged users to access telemetry packets.

5

In which software is CVE-2026-55548 found?

CVE-2026-55548 is found in the Yamcs mission control framework, specifically in the yamcs-core component.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203