Arbitrary WASM Code Execution via AnnotationOverrideFlight Injection in Yoke ATC

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.8 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2026-26056: 0.46% estimated exploitation activity in the next 30 days; percentile 39.51 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Arbitrary WASM Code Execution via AnnotationOverrideFlight Injection in Yoke ATC This vulnerability exists in the Air Traffic Controller (ATC) component of Yoke, a Kubernetes deployment tool. It allows users with CR create/update permissions to execute arbitrary WASM code in the ATC controller context by injecting a malicious URL through the overrides.yoke.cd/flight annotation. The ATC controller downloads and executes the WASM module without proper URL validation, enabling attackers to create arbitrary Kubernetes resources or potentially escalate privileges to cluster-admin level. Recommended CWE: CWE-94 (Improper Control of Generation of Code - Code Injection) Summary Yoke ATC allows users to override the Flight WASM module URL via the overrides.yoke.cd/flight annotation on Custom Resources. The controller only checks if the user has update permission on airways resources but does not validate the WASM URL source. An attacker with CR create/update permissions can inject a malicious…

Published by the source

12 Feb 2026, 22:06 UTC

Last modified by the source

13 Feb 2026, 17:15 UTC

Source last checked

26 Oct 2026, 15:14 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-wj8p-jj64-h7ff

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-26056

Advisory: Arbitrary WASM Code Execution via AnnotationOverrideFlight Injection in Yoke ATC
IDs: CVE-2026-26056, GHSA-wj8p-jj64-h7ff
Record: https://patchnext.com/advisories/cve-2026-26056 (revision 1, source checked 26 Oct 2026, 15:14 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/yokecd/yoke: affected <= 0.19.0

## Suggested inspection (read-only)
- Go github.com/yokecd/yoke: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/yokecd/yoke.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-wj8p-jj64-h7ff (GitHub-reviewed advisory GHSA-wj8p-jj64-h7ff lists affected ranges: Go github.com/yokecd/yoke >=0 <=0.19.0)

Commands are suggestions: review each one before running it.