ETK-2026-2211Zero's internal tracking ID, independent of the CVE number.
waiting for further signalsZero needs more public information before it can validate it.description
yamcs-core versions before 5.13.7 mishandle redirect destinations and authorization-code validation in the built-in login flow. An attacker can take over the session of a user who completes login through an attacker-supplied Yamcs login link, then use that user's API privileges. Exploitation requires persuading an already authenticated operator or other user to complete that login flow.
mitigation
Upgrade org.yamcs:yamcs-core to version 5.13.7 or later. Prioritize restricting access for high-privilege users until the upgrade is deployed.
fixed in 5.13.7
outcome
Contextual: an exploit technique exists, but no deterministic check could cover this one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-10-17 20:12Zghsa: trigger signal, started the run
- 2026-10-17 20:12Z
this entry in the feed
GET /api/v1/feed/ETK-2026-2211
{ "etk_id": "ETK-2026-2211", "cve_id": null, "display_id": "ETK-2026-2211", "ghsa_id": "GHSA-24cm-2vgv-fjj6", "euvd_id": null, "status": "published", "anchor_state": "awaiting_cve", "title": "Authorization-code redirect validation flaw in yamcs-core", "summary": "yamcs-core versions before 5.13.7 mishandle redirect destinations and authorization-code validation in the built-in login flow. An attacker can take over the session of a user who completes login through an attacker-supplied Yamcs login link, then use that user's API privileges. Exploitation requires persuading an already authenticated operator or other user to complete that login flow.", "mitigation": "Upgrade org.yamcs:yamcs-core to version 5.13.7 or later. Prioritize restricting access for high-privilege users until the upgrade is deployed.", "vendor": "maven", "product": "maven:org.yamcs:yamcs-core", "affected": [ { "affected_notes": [], "affected_ranges": [ "<= 5.13.6" ], "ecosystem": "maven", "fixed_versions": [ "5.13.7" ], "package_name": "org.yamcs:yamcs-core", "purl": "pkg:maven/org.yamcs/yamcs-core" } ], "cwes": [ 287 ], "cvss_score": 8.5, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N", "epss_score": null, "epss_percentile": null, "epss_asof": null, "automation": "contextual", "check": false, "check_confidence_basis": null, "exploit": false, "pipeline_minutes": 30.841639083333334, "t0_at": null, "signals": { "public_poc": { "at": "2026-10-17T20:12:51+00:00", "days": -3.3346155415509258, "is_lower_bound": true, "measured_at": "2026-10-21T04:14:41.806081+00:00", "url": "https://github.com/yamcs/yamcs/security/advisories/GHSA-24cm-2vgv-fjj6" }, "trigger_signal": { "at": "2026-10-17T20:12:51+00:00", "days": -3.3346155415509258, "is_lower_bound": true, "measured_at": "2026-10-21T04:14:41.806081+00:00", "url": "https://github.com/yamcs/yamcs/security/advisories/GHSA-24cm-2vgv-fjj6" } } }
published 2026-10-20 19:50Z
last change 2026-10-21 03:59Z
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.