Ignition config accessible to unprivileged software on VMware

Exploitation

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

CVSS

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

EPSS

• CVE-2022-1706: 1.30% estimated exploitation activity in the next 30 days; percentile 70.43 (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 Unprivileged software in VMware VMs, including software running in unprivileged containers, can retrieve an Ignition config stored in a hypervisor guestinfo variable or OVF environment. If the Ignition config contains secrets, this can result in the compromise of sensitive information. Patches Ignition 2.14.0 and later adds a new systemd service, ignition-delete-config.service, that deletes the Ignition config from supported hypervisors (currently VMware and VirtualBox) during the first boot. This ensures that unprivileged software cannot retrieve the Ignition config from the hypervisor. If you have external tooling that requires the Ignition config to remain accessible in VM metadata after provisioning, and your Ignition config does not include sensitive information, you can prevent Ignition 2.14.0 and later from deleting the config by masking ignition-delete-config.service. For example: Workarounds Avoid storing secrets in Ignition configs. In addition to VMware, many cloud…

Published by the source

25 May 2022, 19:37 UTC

Last modified by the source

11 Mar 2026, 19:49 UTC

Source last checked

26 Oct 2026, 15:15 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-hj57-j5cw-2mwp

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

# Patch Next advisory brief: CVE-2022-1706

Advisory: Ignition config accessible to unprivileged software on VMware
IDs: CVE-2022-1706, GHSA-hj57-j5cw-2mwp
Record: https://patchnext.com/advisories/cve-2022-1706 (revision 1, source checked 26 Oct 2026, 15:15 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/coreos/ignition 2.14.0; github.com/coreos/ignition/v2 2.14.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/coreos/ignition: affected <= 0.35.0; fixed in 2.14.0
- Go github.com/coreos/ignition/v2: affected < 2.14.0; fixed in 2.14.0

## Suggested inspection (read-only)
- Go github.com/coreos/ignition: check the installed version with your package manager.
- Go github.com/coreos/ignition/v2: 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/coreos/ignition, github.com/coreos/ignition/v2.
- 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-hj57-j5cw-2mwp (GitHub-reviewed advisory GHSA-hj57-j5cw-2mwp lists affected ranges: Go github.com/coreos/ignition/v2 >=0 =0 <=0.35.0)

Commands are suggestions: review each one before running it.