Skip to content
Fencer Intel
critical 9.8

CVE-2014-4966 json

Ansible Arbitrary Code Execution

published 6y ago modified 4mo ago also GHSA-wqq5-c89p-3wc3 , PYSEC-2020-204 , EUVD-2020-0016

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

Summary

Ansible before 1.6.7 does not prevent inventory data with "{{" and "lookup" substrings, and does not prevent remote data with "{{" substrings, which allows remote attackers to execute arbitrary code via (1) crafted lookup('pipe') calls or (2) crafted Jinja2 data.

Patch / fix

  • pypi ansible 1.6.7
  • redhat ansible 1.6.7
  • ansible Debian 14, Debian 13, Debian 12 1.6.8+dfsg-1

debian advisories DEBIAN-CVE-2014-4966

  • ansible Ubuntu Pro 14.04 LTS 1.5.4+dfsg-1ubuntu0.1~esm2

ubuntu advisories UBUNTU-CVE-2014-4966

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • ansible-14 openSUSE Tumbleweed 14.6.0-1.1
  • ansible-13 openSUSE Tumbleweed 13.7.0-1.1
  • ansible-12 openSUSE Tumbleweed 12.2.0-1.1
  • ansible-11 openSUSE Tumbleweed 11.11.0-1.1
  • ansible-10 openSUSE Tumbleweed 10.6.0-1.1
  • ansible-9 openSUSE Tumbleweed 9.8.0-1.1
  • ansible openSUSE Tumbleweed 2.2.0.0-1.1

opensuse advisories openSUSE-SU-2026:12447-1openSUSE-SU-2026:10944-1openSUSE-SU-2025:15753-1openSUSE-SU-2025:15605-1openSUSE-SU-2024:14536-1openSUSE-SU-2024:14244-1

Is CVE-2014-4966 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-2014-4966 updated cvss 1.4

ansible: multiple flaws

  • Red Hat All currently supported Red Hat products
    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

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
pypi ansible
<1.6.7
1.6.7

Classification

Weakness
  • CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component

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.