Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2020-11987: Apache Batik 1.13 is vulnerable to server-side request forgery, caused by improper input validation by the Nod

63
This week
HIGH 8.2REMOTEWATCHLISTUPGRADEMITIGATEDOWNGRADE

CVE-2020-11987 is a high-severity flaw (CVSS 8.2) affecting batik, fedora, agile engineering data management. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Apache Batik 1.13 is vulnerable to server-side request forgery, caused by improper input validation by the NodePickerPanel. By using a specially-crafted argument, an attacker could exploit this vulnerability to cause the underlying server to make arbitrary GET requests.

Why this priority

  • High severity
  • EPSS top 4%: very likely to be exploited
  • Remotely exploitable, no login, no user action
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score8.2 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance13.6% (top 4%)
CISA exploited listNo
WeaknessCWE-20, CWE-918
Published2021-02-24
Last modified2026-10-08
Publisher (CNA): Apache Software Foundation · Vendor: apache · fedoraproject · oracle

Share: LinkedIn · X · Reddit

Last updated 2026-10-08 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

apache batik UPGRADE
Affected: <= 1.13
Fixed in: newer than 1.13
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy batik || rpm -q batik || batik --version
2. UPGRADE to newer than 1.13 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade batik
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade batik
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
fedoraproject fedora MITIGATE
Affected: 33 · 34
Fixed in: no fixed release known
Safe to downgrade to: a release before 33
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
oracle agile engineering data management DOWNGRADE
Affected: 6.2.1.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 6.2.1.0
1. Check installed version
apt-cache policy agile-engineering-data-management || rpm -q agile-engineering-data-management || agile-engineering-data-management --version
2. No fixed release: DOWNGRADE to a release before 6.2.1.0 (Debian / Ubuntu)
apt-cache madison agile-engineering-data-management sudo apt install agile-engineering-data-management=<VERSION_BEFORE_6.2.1.0> sudo apt-mark hold agile-engineering-data-management
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list agile-engineering-data-management sudo dnf downgrade agile-engineering-data-management-<VERSION_BEFORE_6.2.1.0> sudo dnf versionlock add agile-engineering-data-management
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
oracle banking apis DOWNGRADE
Affected: 18.3 · 19.1 · 19.2 · 20.1 · 21.1
Fixed in: no fixed release known
Safe to downgrade to: a release before 18.3
1. Check installed version
apt-cache policy banking-apis || rpm -q banking-apis || banking-apis --version
2. No fixed release: DOWNGRADE to a release before 18.3 (Debian / Ubuntu)
apt-cache madison banking-apis sudo apt install banking-apis=<VERSION_BEFORE_18.3> sudo apt-mark hold banking-apis
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list banking-apis sudo dnf downgrade banking-apis-<VERSION_BEFORE_18.3> sudo dnf versionlock add banking-apis
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
oracle banking digital experience DOWNGRADE
Affected: 18.3 · 19.1 · 19.2 · 20.1 · 21.1
Fixed in: no fixed release known
Safe to downgrade to: a release before 18.3
1. Check installed version
apt-cache policy banking-digital-experience || rpm -q banking-digital-experience || banking-digital-experience --version
2. No fixed release: DOWNGRADE to a release before 18.3 (Debian / Ubuntu)
apt-cache madison banking-digital-experience sudo apt install banking-digital-experience=<VERSION_BEFORE_18.3> sudo apt-mark hold banking-digital-experience
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list banking-digital-experience sudo dnf downgrade banking-digital-experience-<VERSION_BEFORE_18.3> sudo dnf versionlock add banking-digital-experience
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
oracle communications application session controller DOWNGRADE
Affected: 3.9m0p3
Fixed in: no fixed release known
Safe to downgrade to: a release before 3.9m0p3
1. Check installed version
apt-cache policy communications-application-session-controller || rpm -q communications-application-session-controller || communications-application-session-controller --version
2. No fixed release: DOWNGRADE to a release before 3.9m0p3 (Debian / Ubuntu)
apt-cache madison communications-application-session-controller sudo apt install communications-application-session-controller=<VERSION_BEFORE_3.9m0p3> sudo apt-mark hold communications-application-session-controller
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list communications-application-session-controller sudo dnf downgrade communications-application-session-controller-<VERSION_BEFORE_3.9m0p3> sudo dnf versionlock add communications-application-session-controller
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-11987?

batik: upgrade to newer than 1.13; fedora: mitigate or apply the listed mitigation; agile engineering data management: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2020-11987 being exploited?

CVE-2020-11987 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-11987 affect?

CVE-2020-11987 affects batik, fedora, agile engineering data management. Severity is high (CVSS 8.2). Apache Batik 1.13 is vulnerable to server-side request forgery, caused by improper input validation by the NodePickerPanel. By using a specially-crafted argument, an attacker could exploit this vulnerability to cause the underlying server t

How urgent is CVE-2020-11987?

Priority 63/100. High severity; EPSS top 4%: very likely to be exploited; Remotely exploitable, no login, no user action; On your watchlist

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.