Vela Insecure Defaults

Exploitation

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

CVSS

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

EPSS

• CVE-2022-39395: 1.20% estimated exploitation activity in the next 30 days; percentile 68.16 (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.

Impact Some current default configurations for Vela allow exploitation and container breakouts. Default Privileged Images Running Vela plugins as privileged Docker containers allows a malicious user to easily break out of the container and gain access to the worker host operating system. On a fresh install of Vela without any additional configuration, the target/vela-docker plugin will run as a privileged container, even if the Vela administrators did not intend to allow for any privileged plugins, and even if the vela.yml configuration file does not use the privileged = True flag. Privileged containers permit trivial breakouts, which can pose significant risk to the environment in which Vela is running. Default Allowed Repositories On a fresh install of Vela, anyone with a GitHub account (or other enabled source control management solution) is allowed to enable a repository within Vela and run builds. This means that, if a Vela instance is accessible to the public, a third party…

Published by the source

9 Nov 2022, 19:17 UTC

Last modified by the source

6 Sep 2024, 21:33 UTC

Source last checked

26 Oct 2026, 15:05 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-5m7g-pj8w-7593

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

# Patch Next advisory brief: CVE-2022-39395

Advisory: Vela Insecure Defaults
IDs: CVE-2022-39395, GHSA-5m7g-pj8w-7593
Record: https://patchnext.com/advisories/cve-2022-39395 (revision 1, source checked 26 Oct 2026, 15:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/go-vela/worker 0.16.0; github.com/go-vela/server 0.16.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/go-vela/worker: affected < 0.16.0; fixed in 0.16.0
- Go github.com/go-vela/server: affected < 0.16.0; fixed in 0.16.0

## Suggested inspection (read-only)
- Go github.com/go-vela/worker: check the installed version with your package manager.
- Go github.com/go-vela/server: 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/go-vela/worker, github.com/go-vela/server.
- 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-5m7g-pj8w-7593 (GitHub-reviewed advisory GHSA-5m7g-pj8w-7593 lists affected ranges: Go github.com/go-vela/server >=0 =0 <0.16.0)

Commands are suggestions: review each one before running it.