CVE-2026-55548

MEDIUMPre-NVD 4.34.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (29th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-44960 (ENISA EUVD) · GHSA-8xjq-pr36-ccgf (GitHub Security Advisories)Source: ENISA EUVD

4.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 4.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
4.3
EG Score
4.3MEDIUMmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity43% × 45%
Impact severity (EG Severity): CVSS 4.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
29th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (4.3): severity, escalated by confirmed exploitation. This CVE's 4.3 is its impact severity (EG Severity), not escalated.

EG Severity
4.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 16, 2026

Last Modified

July 20, 2026

Advisory Details (5)

Auto-updated Jul 20, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)

Insecure Direct Object Reference (IDOR) in PacketsApi allows unprivileged users to dump all telemetry packets · Advisory · yamcs/yamcs · GitHub

https://github.com/yamcs/yamcs/security/advisories/GHSA-8xjq-pr36-ccgf
GitHub release Patch Available

Yamcs 5.13.2

Patch available: yamcs/yamcs yamcs-5.13.2

https://github.com/yamcs/yamcs/releases/tag/yamcs-5.13.2
GitHub release Patch Available

Yamcs 5.12.8

Patch available: yamcs/yamcs yamcs-5.12.8

https://github.com/yamcs/yamcs/releases/tag/yamcs-5.12.8
GitHub commit

commit c743cc3acf5b (yamcs/yamcs)

Fix landed in yamcs/yamcs commit c743cc3acf5b — awaiting tagged release

https://github.com/yamcs/yamcs/commit/c743cc3acf5b5c53ff5181b94eacc21340f70dd9
GitHub commit

commit b566beceba98 (yamcs/yamcs)

Fix landed in yamcs/yamcs commit b566beceba98 — awaiting tagged release

https://github.com/yamcs/yamcs/commit/b566beceba98cc35514b0e1519be126b8c5a0438

Vendor Advisories for CVE-2026-55548(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.yamcs:yamcs-core0.29.3 ... 5.9.9 (166 versions)
  • 5.13.0 up to 5.13.2: fixed in 5.13.2
  • every version up to 5.12.8: fixed in 5.12.8
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 39× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 143 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 43 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  2. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  3. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  4. 2026-10-25 14:18 UTCEG score recompute
  5. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  6. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  7. 2026-10-22 21:15 UTCEG score recompute
  8. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  9. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  10. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  11. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  12. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  13. 2026-10-18 03:30 UTCEG score recompute
  14. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  15. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  16. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  17. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  18. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  19. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  20. 2026-10-12 15:55 UTCEG score recompute
  21. 2026-10-11 19:39 UTCEG score recompute
  22. 2026-10-11 16:54 UTCEG score recompute
  23. 2026-10-11 14:17 UTCEG score recompute
  24. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  25. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 27th percentile
Show 75 more
  1. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  2. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  3. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  4. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  5. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  6. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  7. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  8. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  9. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  10. 2026-10-01 11:23 UTCEG score recompute
  11. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  12. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  13. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  14. 2026-09-28 08:18 UTCEG score recompute
  15. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  16. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  17. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  18. 2026-09-24 08:29 UTCEG score recompute
  19. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  20. 2026-09-23 03:02 UTCEG score recompute
  21. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  22. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  23. 2026-09-18 04:38 UTCEG score recompute
  24. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  25. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  26. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  27. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  28. 2026-09-14 06:08 UTCEG score recompute
  29. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  30. 2026-09-13 07:08 UTCEG score recompute
  31. 2026-09-11 21:40 UTCEG score recompute
  32. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  33. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  34. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  35. 2026-09-08 00:29 UTCEG score recompute
  36. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  37. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  38. 2026-09-05 20:38 UTCEG score recompute
  39. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  40. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  41. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  42. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  43. 2026-08-31 02:41 UTCEG score recompute
  44. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  45. 2026-08-30 03:34 UTCEG score recompute
  46. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  47. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  48. 2026-08-27 21:51 UTCEG score recompute
  49. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  50. 2026-08-26 22:51 UTCEG score recompute
  51. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  52. 2026-08-25 18:55 UTCEG score recompute
  53. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  54. 2026-08-24 19:21 UTCEG score recompute
  55. 2026-08-23 19:57 UTCEG score recompute
  56. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  57. 2026-08-22 20:57 UTCEG score recompute
  58. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  59. 2026-08-20 22:55 UTCEG score recompute
  60. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  61. 2026-08-19 23:55 UTCEG score recompute
  62. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  63. 2026-08-18 19:56 UTCEG score recompute
  64. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  65. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  66. 2026-08-17 13:23 UTCEG score recompute
  67. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  68. 2026-08-16 14:23 UTCEG score recompute
  69. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  70. 2026-08-15 15:23 UTCEG score recompute
  71. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  72. 2026-08-14 16:22 UTCEG score recompute
  73. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  74. 2026-08-12 18:21 UTCEG score recompute
  75. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.2% · 16th percentile

Frequently asked(5)

What is CVE-2026-55548?
CVE-2026-55548 is a medium-severity vulnerability; its CVE record was published on July 16, 2026. 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…
When was the CVE record for CVE-2026-55548 published?
The CVE record for CVE-2026-55548 was published on July 16, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 20, 2026; the record at its source may have been updated since.
Is CVE-2026-55548 actively exploited?
CVE-2026-55548 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (29th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55548?
CVE-2026-55548 has a CVSS base score of 4.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55548?
A fix for CVE-2026-55548 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55548 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55548

Explore →

Is Your Infrastructure Affected by CVE-2026-55548?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.