How severe is CVE-2020-1945?

CVE-2020-1945 has a CVSS score of 6.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2020-1945?

CVE-2020-1945 affects the following packages: org.apache.ant:ant (Maven), org.apache.ant:ant (Maven). Ecosystems affected: Maven.

How do I fix CVE-2020-1945?

Update org.apache.ant:ant to 1.9.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-1945 is resolved across your whole dependency graph.

How do I detect CVE-2020-1945 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.ant:ant, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2020-1945 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2020-1945 actively exploited in the wild?

No public exploit code has been indexed for CVE-2020-1945 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2020-1945?

CVE-2020-1945 has an EPSS (Exploit Prediction Scoring System) score of 1.8%, placing it in the 77th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2020-1945?

CVE-2020-1945 is classified as CWE-668 (CWE-668). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2020-1945 published, and has it been updated?

CVE-2020-1945 was published on May 14, 2020 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2020-1945 — ant

MEDIUM

CVE-2020-1945 is a medium-severity (CVSS 6.3) CWE-668 vulnerability in org.apache.ant:ant. A fix is available for org.apache.ant:ant — see the affected versions and patch details below.

Sensitive Data Exposure in Apache Ant

Also known asGHSA-4p6w-m9wc-c9c9

Published

May 14, 2020

Updated

Jul 8, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs77th percentile — riskier than 77% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2020-1945 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected

☕org.apache.ant:ant☕org.apache.ant:ant

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Apache Ant 1.1 to 1.9.14 and 1.10.0 to 1.10.7 uses the default temporary directory identified by the Java system property java.io.tmpdir for several tasks and may thus leak sensitive information. The fixcrlf and replaceregexp tasks also copy files from the temporary directory back into the build tree allowing an attacker to inject modified source files into the build process.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.ant:ant`	≥ 1.1&&< 1.9.15	1.9.15`org.apache.ant:ant:1.9.15`
☕Maven	`org.apache.ant:ant`	≥ 1.10.0&&< 1.10.8	1.10.8`org.apache.ant:ant:1.10.8`

Affected Products

50 products · 117 configurations

Application

antapache

≥ 1.10.0 && ≤ 1.10.7

range

ubuntu linuxcanonical

1 version

19.10

fedorafedoraproject

2 versions

3132

leapopensuse

1 version

15.2

Application

agile engineering data managementoracle

1 version

6.2.1.0

Application

banking enterprise collectionsoracle

≥ 2.7.0 && ≤ 2.9.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.ant:ant, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.ant:ant to 1.9.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-1945 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

In OpenShift Container Platform (OCP), the Hive/Presto/Hadoop components that comprise the OCP Metering stack, ship the vulnerable version of ant package. Since the release of OCP 4.6, the Metering product has been deprecated [1], hence the affected components are marked as wontfix. This may be fixed in the…

Workaround published by Red Hat

For versions 1.1 to 1.9.14 and 1.10.0 to 1.10.7, set the java.io.tmpdir system property to a private directory-- only readable and writable by the current user-- before running Ant. For versions 1.9.15 and 1.10.8, use the Ant property ant.tmpfile instead. Ant 1.10.8 protects the temporary files if the underlying filesystem allows it, but using a private temporary directory is still recommended.

Source: Red Hat security advisory for CVE-2020-1945 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat AMQ Streams 1.5.0	`ant`	RHSA-2020:2618
Red Hat OpenShift Container Platform 3.11	`jenkins-0:2.263.3.1612433584-1.el7`	RHSA-2021:0637
Red Hat OpenShift Container Platform 4.5	`conmon-2:2.0.21-1.rhaos4.5.el7`	RHSA-2021:0429
Red Hat OpenShift Container Platform 4.6	`jenkins-0:2.263.3.1612434510-1.el8`	RHSA-2021:0423
RHDM 7.9.0	`ant`	RHSA-2020:4960
RHPAM 7.9.0	`ant`	RHSA-2020:4961

UbuntuMEDIUM

USN-4380-1Ubuntu USN-4874-1Ubuntu

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2020-1945 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2020-1945 — ant

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2020-1945 in your dependencies?