CVE-2026-55548: Yamcs Insecure Direct Object Reference (IDOR) Vulnerability
MODERATECVE-2026-55548 is a MODERATE (CVSS 4.3) insecure direct object reference (idor) vulnerability (CWE-284: Improper Access Control) affecting Yamcs libraries in the Maven ecosystem. The issue involves insecure direct object reference (idor) in packetsapi allows unprivileged users to dump all telemetry packets. Remediation is available by upgrading affected packages to version 5.13.2, 5.12.8.
CVE-2026-55548 at a Glance
Security Impact
CVSS: 4.3
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N).
How to Fix CVE-2026-55548
To remediate this vulnerability, upgrade all affected Yamcs dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
<dependency>
<groupId>org.yamcs</groupId>
<artifactId>yamcs-core</artifactId>
<version>5.13.2</version>
</dependency>
<dependency>
<groupId>org.yamcs</groupId>
<artifactId>yamcs-core</artifactId>
<version>5.12.8</version>
</dependency>
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree -Dincludes=org.yamcs
How to Check if You Are Affected
To determine whether your Java application is affected by CVE-2026-55548, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree -Dincludes=org.yamcs
Analyze the terminal output to locate any version of Yamcs in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 5.13.2), your application is affected.
Note: The mvn dependency:tree -Dincludes=org.yamcs command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-284: Improper Access Control, where the product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. In Yamcs, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-55548 Affected Yamcs Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
org.yamcs:yamcs-core
|
Maven |
≥ 5.13.0
< 5.13.2
|
5.13.2
|
|
org.yamcs:yamcs-core
|
Maven |
< 5.12.8
|
5.12.8
|
References
Frequently Asked Questions
What is CVE-2026-55548?
Which Yamcs versions are affected?
What version fixes CVE-2026-55548?
Is yamcs-core affected?
What is the CVSS score of CVE-2026-55548?
What CWE is associated with CVE-2026-55548?
How can I check Maven dependencies for CVE-2026-55548?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-8xjq-pr36-ccgf",
"modified" : "2026-08-28T17:15:02Z",
"published" : "2026-08-28T17:15:01Z",
"aliases" : [ "CVE-2026-55548" ],
"summary" : "Yamcs: Insecure Direct Object Reference (IDOR) in PacketsApi allows unprivileged users to dump all telemetry packets",
"details" : "## Summary\nThe `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.\n\n## Vulnerability Details\nIn `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.\n\n```java\n @Override\n public void exportPackets(Context ctx, ExportPacketsRequest request, Observer<HttpBody> observer) {\n String instance = InstancesApi.verifyInstance(request.getInstance());\n\n Set<String> nameSet = new HashSet<>(request.getNameList());\n ctx.checkObjectPrivileges(ObjectPrivilegeType.ReadPacket, nameSet);\n\n SqlBuilder sqlb = new SqlBuilder(XtceTmRecorder.TABLE_NAME);\n \n // ... time filters ...\n\n if (request.getNameCount() > 0) {\n sqlb.whereColIn(\"pname\", nameSet);\n }\n String sql = sqlb.toString();\n // ...\n```\nThe 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`. \n\nSince `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).\n\nFinally, the query is executed and the results are streamed back to the user:\n```java\n StreamFactory.stream(instance, sql, sqlb.getQueryArguments(), new StreamSubscriber() {\n\n @Override\n public void onTuple(Stream stream, Tuple tuple) {\n if (observer.isCancelled()) {\n stream.close();\n return;\n }\n\n byte[] raw = (byte[]) tuple.getColumn(StandardTupleDefinitions.TM_PACKET_COLUMN);\n HttpBody body = HttpBody.newBuilder()\n .setData(ByteString.copyFrom(raw))\n .build();\n observer.next(body);\n }\n // ...\n```\nCrucially, 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**. \n\nThus, a user who possesses no `ReadPacket` privileges at all can easily bypass authorization and extract all telemetry data from the archive.\n\n## Steps to Reproduce\n1. Start the Yamcs server (e.g., using the `simulation` example) with authentication enforced.\n2. Log in as a low-privileged user (or use their credentials) who does **not** have the `ReadPacket` privilege.\n3. Send an HTTP GET request to the export packets endpoint without specifying any `name` parameters:\n ```bash\n curl -v -u low_priv_user:password \"http://localhost:8090/api/archive/simulator:exportPackets\" -o dumped_packets.raw\n ```\n4. Observe that the server responds with HTTP `200 OK` and streams all raw packets to the response, saving them to `dumped_packets.raw`. \n5. The downloaded file contains raw CCSDS Space Packets (binary telemetry data).\n6. 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.\n\n## Impact\nTelemetry 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.\n\n## Remediation\nEnsure that `exportPackets` enforces the same per-row privilege checks as `streamPackets`. \nUpdate the `onTuple` handler to check the user's privileges before emitting each packet:\n\n```java\n @Override\n public void onTuple(Stream stream, Tuple tuple) {\n if (observer.isCancelled()) {\n stream.close();\n return;\n }\n\n // FIX: Retrieve packet name and check authorization\n String pname = (String) tuple.getColumn(XtceTmRecorder.PNAME_COLUMN);\n if (ctx.user.hasObjectPrivilege(ObjectPrivilegeType.ReadPacket, pname)) {\n byte[] raw = (byte[]) tuple.getColumn(StandardTupleDefinitions.TM_PACKET_COLUMN);\n HttpBody body = HttpBody.newBuilder()\n .setData(ByteString.copyFrom(raw))\n .build();\n observer.next(body);\n }\n }\n```\n\n## System Information\n- **Affected Versions:** 5.13.0 (Latest Release), 5.12.x, and current `master` branch.\n- **Tested Revision (master):** `309218c651680f79df11a8d0f8628f7033f98a83` \n- **Vulnerability Type:** Insecure Direct Object Reference (IDOR) / Logical Authorization Bypass\n\n## PoC Images:\n\n- Check version:\n<img width=\"1157\" height=\"489\" alt=\"image\" src=\"https://github.com/user-attachments/assets/58608222-b76f-4eb4-8e57-423523062992\" />\n\n- Check privilege of user:\n<img width=\"1439\" height=\"953\" alt=\"image\" src=\"https://github.com/user-attachments/assets/aa7e55f2-2460-4f24-8b6f-d461d2499a6f\" />\n<img width=\"1214\" height=\"224\" alt=\"image\" src=\"https://github.com/user-attachments/assets/e9123ae3-a194-462d-a5ca-2c0b1cc9cc6f\" />\n\n\n- Exploit:\n\n\n<img width=\"1728\" height=\"685\" alt=\"image\" src=\"https://github.com/user-attachments/assets/0c7b3099-44d6-4392-bbaa-8e84cc151784\" />\n\n<img width=\"1768\" height=\"797\" alt=\"image\" src=\"https://github.com/user-attachments/assets/df4016a5-d460-4611-a34a-8c0d206edd9c\" />",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Maven",
"name" : "org.yamcs:yamcs-core"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "5.13.0"
}, {
"fixed" : "5.13.2"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 5.13.1"
}
}, {
"package" : {
"ecosystem" : "Maven",
"name" : "org.yamcs:yamcs-core"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "5.12.8"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 5.12.7"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/yamcs/yamcs/security/advisories/GHSA-8xjq-pr36-ccgf"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-55548"
}, {
"type" : "WEB",
"url" : "https://github.com/yamcs/yamcs/commit/b566beceba98cc35514b0e1519be126b8c5a0438"
}, {
"type" : "WEB",
"url" : "https://github.com/yamcs/yamcs/commit/c743cc3acf5b5c53ff5181b94eacc21340f70dd9"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/yamcs/yamcs"
}, {
"type" : "WEB",
"url" : "https://github.com/yamcs/yamcs/releases/tag/yamcs-5.12.8"
}, {
"type" : "WEB",
"url" : "https://github.com/yamcs/yamcs/releases/tag/yamcs-5.13.2"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-284", "CWE-862" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-08-28T17:15:01Z",
"nvd_published_at" : "2026-07-16T17:16:57Z"
}
}