Skip to content
Fencer Intel
critical 9.1

CVE-2020-27195 json

Use After Free in HashiCorp Nomad

published 6y ago modified 4mo ago also GHSA-77cr-6gr8-7rr9 , GO-2022-0806 , EUVD-2022-0884

cvss
9.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.5%
EPSS 1.5% chance of exploitation in 30 days, percentile 74%
public exploits
0
none known

Summary

HashiCorp Nomad and Nomad Enterprise version 0.9.0 up to 0.12.5 client file sandbox feature can be subverted using either the template or artifact stanzas. Fixed in 0.12.6, 0.11.5, and 0.10.6

Patch / fix

  • go github.com/hashicorp/nomad 0.10.6, 0.11.5, 0.12.6
  • nomad Alpine 3.18, Alpine 3.17, Alpine 3.16 +2 more 0.12.7-r0

alpine advisories ALPINE-CVE-2020-27195

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2020-27195 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-27195 updated cvss 7.1

nomad: file sandbox escape via template and artifact stanzas

  • Red Hat Advanced Cluster Management for Kubernetes 2 nomad
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.49% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
NVD 2.0 6.4 AV:N/AC:L/Au:N/C:P/I:P/A:N
GitHub 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
go github.com/hashicorp/nomad
>=0.9.0, <0.10.6
>=0.11.0, <0.11.5
>=0.12.0, <0.12.6
0.10.6
0.11.5
0.12.6

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.