CVE-2026-55559

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

GHSA-73mf-m39p-wpm9 ↗EUVD-2026-67843 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+2h36mkevAttacks confirmed in the real world.+78d
spaceapplications yamcs <= 5.13.1; <= 5.12.7
fixed in 5.13.2, 5.12.8
ETK-2026-4486Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:maven/org.yamcs/yamcs-core
3d 22h 58msince last run
13mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
cve.org publicationpublic poc+0.1dtrigger signal +77dkev+78dwaiting for further signals
0
+20d
+40d
+60d

description

Yamcs versions before 5.12.8 and 5.13.2 mishandle template arguments supplied to the instance creation and update APIs. An attacker can inject configuration that causes commands to run as the Yamcs service account; this requires the CreateInstances privilege on secured deployments, but may be unauthenticated when security.yaml is absent.

mitigation

Upgrade Yamcs to 5.12.8, 5.13.2, or a later release. Configure security.yaml and restrict CreateInstances to trusted administrators until the upgrade is complete.

fixed in 5.13.2, 5.12.8

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.78%56th percentile
agent run time
13m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-08-28 17:22Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+2h36m
Δ to kevAttacks confirmed in the real world.
+78d

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-08-28 17:22Z
  2. 2026-11-14
    vulncheck_kev: trigger signal, started the run
  3. 2026-11-14 00:00Z
  4. 2026-11-14 23:17Z

this entry in the feed

GET /api/v1/feed/CVE-2026-55559

{
  "etk_id": "ETK-2026-4486",
  "cve_id": "CVE-2026-55559",
  "display_id": "CVE-2026-55559",
  "ghsa_id": "GHSA-73mf-m39p-wpm9",
  "euvd_id": "EUVD-2026-67843",
  "status": "published",
  "anchor_state": "anchored",
  "title": "YAML injection in Yamcs instance templates",
  "summary": "Yamcs versions before 5.12.8 and 5.13.2 mishandle template arguments supplied to the instance creation and update APIs. An attacker can inject configuration that causes commands to run as the Yamcs service account; this requires the CreateInstances privilege on secured deployments, but may be unauthenticated when security.yaml is absent.",
  "mitigation": "Upgrade Yamcs to 5.12.8, 5.13.2, or a later release. Configure security.yaml and restrict CreateInstances to trusted administrators until the upgrade is complete.",
  "vendor": "spaceapplications",
  "product": "yamcs",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 5.13.1"
      ],
      "ecosystem": "maven",
      "fixed_versions": [
        "5.13.2"
      ],
      "package_name": "org.yamcs:yamcs-core",
      "purl": "pkg:maven/org.yamcs/yamcs-core"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 5.12.7"
      ],
      "ecosystem": "maven",
      "fixed_versions": [
        "5.12.8"
      ],
      "package_name": "org.yamcs:yamcs-core",
      "purl": "pkg:maven/org.yamcs/yamcs-core"
    }
  ],
  "cwes": null,
  "cvss_score": 9.8,
  "cvss_src": "other",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0078,
  "epss_percentile": 0.5666,
  "epss_asof": "2026-11-17",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 12.806171133333333,
  "t0_at": "2026-08-28T17:22:07.633000+00:00",
  "signals": {
    "kev": {
      "at": "2026-11-14T00:00:00+00:00",
      "days": 78,
      "is_lower_bound": false,
      "measured_at": "2026-08-28T17:22:07.633000+00:00",
      "precision": "day",
      "url": "https://vulncheck.com/cve/CVE-2026-55559"
    },
    "public_poc": {
      "at": "2026-08-28T19:58:04.713000+00:00",
      "days": 0.10829953703703704,
      "is_lower_bound": false,
      "measured_at": "2026-08-28T17:22:07.633000+00:00",
      "url": "https://github.com/yamcs/yamcs/security/advisories/GHSA-73mf-m39p-wpm9"
    },
    "trigger_signal": {
      "at": "2026-11-14T00:00:00+00:00",
      "days": 77.27630054398148,
      "is_lower_bound": false,
      "measured_at": "2026-08-28T17:22:07.633000+00:00",
      "url": "https://vulncheck.com/cve/CVE-2026-55559"
    }
  }
}

published 2026-11-14 22:54Z
last change 2026-11-18 21:29Z

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.