ETK-2026-4540Zero's internal tracking ID, independent of the CVE number.

waiting for further signalsZero needs more public information before it can validate it.

GHSA-q48q-3338-9mwh ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
maven:org.yamcs:yamcs-core < 5.14.1
fixed in 5.14.1
CWE-94 Improper Control of Generation of Code ('Code Injection')
ETK-2026-4540Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:maven/org.yamcs/yamcs-core
3d 02h 26msince last run
39mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0dwaiting for further signals+0.0d
0
+1d
+2d
+3d

description

Yamcs core before 5.14.1 can incorporate untrusted table column names into generated code during aggregate processing. An authenticated user with table-writing access can introduce the dangerous metadata, and archive-control access is required to trigger execution; these privileges may belong to separate users.

mitigation

Upgrade org.yamcs:yamcs-core to version 5.14.1 or later. Until upgraded, limit both table-writing and archive-control permissions to fully trusted accounts.

fixed in 5.14.1

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, high privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
39m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-15 16:04Z

this entry in the feed

GET /api/v1/feed/ETK-2026-4540

{
  "etk_id": "ETK-2026-4540",
  "cve_id": null,
  "display_id": "ETK-2026-4540",
  "ghsa_id": "GHSA-q48q-3338-9mwh",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Code injection through Yamcs table column names",
  "summary": "Yamcs core before 5.14.1 can incorporate untrusted table column names into generated code during aggregate processing. An authenticated user with table-writing access can introduce the dangerous metadata, and archive-control access is required to trigger execution; these privileges may belong to separate users.",
  "mitigation": "Upgrade org.yamcs:yamcs-core to version 5.14.1 or later. Until upgraded, limit both table-writing and archive-control permissions to fully trusted accounts.",
  "vendor": "maven",
  "product": "maven:org.yamcs:yamcs-core",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 5.14.1"
      ],
      "ecosystem": "maven",
      "fixed_versions": [
        "5.14.1"
      ],
      "package_name": "org.yamcs:yamcs-core",
      "purl": "pkg:maven/org.yamcs/yamcs-core"
    }
  ],
  "cwes": [
    94
  ],
  "cvss_score": 9.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 39.13343581666667,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-11-15T16:04:01+00:00",
      "days": -3.1115252913773146,
      "is_lower_bound": true,
      "measured_at": "2026-11-18T18:44:36.833195+00:00",
      "url": "https://github.com/yamcs/yamcs/security/advisories/GHSA-q48q-3338-9mwh"
    }
  }
}

published 2026-11-15 18:50Z
last change 2026-11-18 18:22Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.