CVE-2020-36641: A vulnerability classified as problematic was found in gturri aXMLRPC up to 1.12.0

Q: How do I fix CVE-2020-36641?

axmlrpc: upgrade to newer than 1.12.1. Exact commands for each OS are on this page.

Q: Is CVE-2020-36641 being exploited?

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

Q: What does CVE-2020-36641 affect?

CVE-2020-36641 affects axmlrpc. Severity is medium (CVSS 5.5). A vulnerability classified as problematic was found in gturri aXMLRPC up to 1.12.0. This vulnerability affects the function ResponseParser of the file src/main/java/de/timroes/axmlrpc/ResponseParser.java. The manipulation leads to xml exter

Q: How urgent is CVE-2020-36641?

Priority 34/100. No elevated risk signals yet.

Routine

MEDIUM 5.5UPGRADE

CVE-2020-36641 is a medium-severity flaw (CVSS 5.5) affecting axmlrpc. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability classified as problematic was found in gturri aXMLRPC up to 1.12.0. This vulnerability affects the function ResponseParser of the file src/main/java/de/timroes/axmlrpc/ResponseParser.java. The manipulation leads to xml external entity reference. Upgrading to version 1.14.0 is able to address this issue. The patch is identified as 456752ebc1ef4c0db980cb5b01a0b3cd0a9e0bae. It is recommended to upgrade the affected component. VDB-217

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.5 (Medium)
Attack vector	Adjacent network
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.9% (top 41%)
CISA exploited list	No
Weakness	CWE-611
Published	2023-01-05
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: gturri

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

Am I affected?

Timeline

2023-01-05 12:15 UTCPublished CVE record published
2026-06-17 03:15 UTCUpdated Record last modified

gturri axmlrpc UPGRADE

Affected: <= 1.12.1

Fixed in: newer than 1.12.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy axmlrpc || rpm -q axmlrpc || axmlrpc --version

2. UPGRADE to newer than 1.12.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade axmlrpc

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade axmlrpc

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

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-36641?

axmlrpc: upgrade to newer than 1.12.1. Exact commands for each OS are on this page.

Is CVE-2020-36641 being exploited?

CVE-2020-36641 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-36641 affect?

CVE-2020-36641 affects axmlrpc. Severity is medium (CVSS 5.5). A vulnerability classified as problematic was found in gturri aXMLRPC up to 1.12.0. This vulnerability affects the function ResponseParser of the file src/main/java/de/timroes/axmlrpc/ResponseParser.java. The manipulation leads to xml exter

How urgent is CVE-2020-36641?

Priority 34/100. No elevated risk signals yet.

Software pages

Java vulnerabilities

References

← Back to latest CVEs