CVE-2013-4260

NONECVSS 0.0

0.0

lib/ansible/playbook/__init__.py in Ansible 1.2.x before 1.2.3, when playbook does not run due to an error, allows local users to overwrite arbitrary files via a symlink attack on a retry file with a predictable name in /var/tmp/ansible/.

CVSS v3: —
EG Score: 0.0(none)
EPSS: 24.2%
KEV: Not listed

Published

September 16, 2013

Last Modified

April 29, 2026

References (8)

secalert@redhathttp://www.ansible.com/security
secalert@redhathttps://bugzilla.redhat.com/show_bug.cgi?id=998227
secalert@redhathttps://exchange.xforce.ibmcloud.com/vulnerabilities/86898
secalert@redhathttps://groups.google.com/forum/#%21topic/ansible-project/UVDYW0HGcNg
af854a3a-2127-422b-91ae-364da2661108http://www.ansible.com/security
af854a3a-2127-422b-91ae-364da2661108https://bugzilla.redhat.com/show_bug.cgi?id=998227
af854a3a-2127-422b-91ae-364da2661108https://exchange.xforce.ibmcloud.com/vulnerabilities/86898
af854a3a-2127-422b-91ae-364da2661108https://groups.google.com/forum/#%21topic/ansible-project/UVDYW0HGcNg

Affected Packages

(1 across 1 ecosystem)

PyPI(1)

Package	Vulnerable range	Fixed in	Dependents
ansible	1.2, 1.2.1, 1.2.2	1.2.3	—

Data Freshness Timeline

(refreshed 14× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:10 UTCepss_batch
2026-06-02 20:10 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:41 UTCepss_batch
2026-05-29 13:41 UTCepss_batch
2026-05-28 22:28 UTCEG score recompute
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-26 13:41 UTCepss_batch
2026-05-26 13:41 UTCepss_batch
2026-05-26 07:16 UTCepss_batch
2026-05-26 07:16 UTCepss_batch

Frequently asked(4)

What is CVE-2013-4260?

CVE-2013-4260 is a none vulnerability published on September 16, 2013. lib/ansible/playbook/init.py in Ansible 1.2.x before 1.2.3, when playbook does not run due to an error, allows local users to overwrite arbitrary files via a symlink attack on a retry file with a predictable name in /var/tmp/ansible/.

When was CVE-2013-4260 disclosed?

CVE-2013-4260 was first published in the National Vulnerability Database on September 16, 2013, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2013-4260 actively exploited?

CVE-2013-4260 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 24.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

How do I remediate CVE-2013-4260?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2013-4260, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2013-4260

Explore →

Is Your Infrastructure Affected by CVE-2013-4260?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2013-4260

📅 Published

🔄 Last Modified

🔗 References (8)