CVE-2023-5764 | Ansible: template injection

A template injection flaw was found in Ansible where a user's controller internal templating operations may remove the unsafe designation from template data. This issue could allow an attacker to use a specially crafted file to introduce templating injection when supplying templating data.

Published: 2023-12-12 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-5764 is rated Moderate Risk (43.2/100): CVSS High severity, with low exploitation likelihood (EPSS 0.54%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2023-5764

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.07% 0.54% +0.47%
2 2025-11-21 0.23% 0.07% -0.17%
3 2025-11-18 — 0.23% —

Full EPSS history (13 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-5764

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.1 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 1.8 5.2 [email protected]
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]

Weakness enumeration for CVE-2023-5764

GitHub Security Advisory for CVE-2023-5764

GHSA-7j69-qfc3-2fq9 · Severity: medium · Ecosystem: pip — Ansible template injection vulnerability

OS Trackers for CVE-2023-5764

vendor priority summary link
debian not yet assigned CVE-2023-5764 not yet assigned priority: Debian including 2 source packages (ansible, ansible-core), 9 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 9. https://security-tracker.debian.org/tracker/CVE-2023-5764
redhat medium — https://access.redhat.com/security/cve/CVE-2023-5764
suse medium CVE-2023-5764 severity moderate: SUSE including 21 source package names (ansible, ansible-2.9.27-150000.1.17.2, …), 38 product×package rows across 15 product lines (HPE Helion OpenStack 8, SUSE Linux Enterprise Module for Open Buildservice Development Tools 15 SP7, … (15 product lines)): Fixed 24, Known Not Affected 14. https://www.suse.com/security/cve/CVE-2023-5764/
ubuntu medium CVE-2023-5764 medium priority: Ubuntu including 2 source packages (ansible, ansible-core), 24 status rows across 12 suites (bionic, focal, jammy, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): not-affected 7, released 5, DNE 4, ignored 4, needs-triage 4. https://ubuntu.com/security/CVE-2023-5764

Affected software / configurations for CVE-2023-5764

Vendor Product Version Raw CPE
redhat ansible < 2.14.12 cpe:2.3:a:redhat:ansible:*:*:*:*:*:*:*:*
redhat ansible >= 2.15.0, < 2.15.7 cpe:2.3:a:redhat:ansible:*:*:*:*:*:*:*:*
redhat ansible 2.16.0 cpe:2.3:a:redhat:ansible:2.16.0:-:*:*:*:*:*:*
redhat ansible 2.16.0 cpe:2.3:a:redhat:ansible:2.16.0:beta1:*:*:*:*:*:*
redhat ansible 2.16.0 cpe:2.3:a:redhat:ansible:2.16.0:beta2:*:*:*:*:*:*
redhat ansible 2.16.0 cpe:2.3:a:redhat:ansible:2.16.0:rc1:*:*:*:*:*:*
fedoraproject extra_packages_for_enterprise_linux 8.0 cpe:2.3:a:fedoraproject:extra_packages_for_enterprise_linux:8.0:*:*:*:*:*:*:*
fedoraproject fedora 38 cpe:2.3:o:fedoraproject:fedora:38:*:*:*:*:*:*:*
fedoraproject fedora 39 cpe:2.3:o:fedoraproject:fedora:39:*:*:*:*:*:*:*
redhat ansible_automation_platform 2.4 cpe:2.3:a:redhat:ansible_automation_platform:2.4:*:*:*:*:*:*:*
redhat ansible_developer 1.1 cpe:2.3:a:redhat:ansible_developer:1.1:*:*:*:*:*:*:*
redhat ansible_inside 1.2 cpe:2.3:a:redhat:ansible_inside:1.2:*:*:*:*:*:*:*

References for CVE-2023-5764

cvelogic Threat Intelligence