Contras Affected by CopyFile Policy Subversion via Symlinks

Exploitation

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

CVSS

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

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Impact The Kata agent policies generated by the Contrast CLI had an issue in the CopyFile verification, which allowed arbitrary writes to the guest root filesytem. A malicious process on the host with the capability to connect to the Kata agent VSOCK could connect to the agent and issue a series of CopyFile requests to overwrite security-critical files or trick the workload into disclosing sensitive data, which effectively amounts to a full guest takeover. Patches This issue has been patched in Contrast v1.19.1. Note that this fix does not change the fact that host-provided content is generally not trustworthy, as documented. Workarounds If upgrading is not possible, users can implement the fix in rego and pass it to contrast generate --policy. The rego-only fix is a bit trickier than the patch, because the data to check is binary. See the references for details. Resources Upstream GHSA: https://github.com/kata-containers/kata-containers/security/advisories/GHSA-q49m-57vm-c8cc…

Published by the source

30 Apr 2026, 20:57 UTC

Last modified by the source

30 Apr 2026, 20:57 UTC

Source last checked

26 Oct 2026, 15:19 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-rh99-wc69-c255

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

# Patch Next advisory brief: GHSA-rh99-wc69-c255

Advisory: Contras Affected by CopyFile Policy Subversion via Symlinks
IDs: GHSA-rh99-wc69-c255
Record: https://patchnext.com/advisories/ghsa-rh99-wc69-c255 (revision 1, source checked 26 Oct 2026, 15:19 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/edgelesssys/contrast 1.19.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/edgelesssys/contrast: affected < 1.19.1; fixed in 1.19.1

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

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/edgelesssys/contrast.
- 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-rh99-wc69-c255 (GitHub-reviewed advisory GHSA-rh99-wc69-c255 lists affected ranges: Go github.com/edgelesssys/contrast >=0 <1.19.1)

Commands are suggestions: review each one before running it.