CVE-2020-25614: xmlquery before 1.3.1 lacks a check for whether a LoadURL response is in the XML format, which allows attacker

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

xmlquery: upgrade to 1.3.1. Exact commands for each OS are on this page.

Q: Is CVE-2020-25614 being exploited?

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

CVE-2020-25614 affects xmlquery. Severity is critical (CVSS 9.8). xmlquery before 1.3.1 lacks a check for whether a LoadURL response is in the XML format, which allows attackers to cause a denial of service (SIGSEGV) at xmlquery.(*Node).InnerText or possibly have unspecified other impact.

Q: How urgent is CVE-2020-25614?

Priority 64/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

CRITICAL 9.8REMOTEUPGRADE

CVE-2020-25614 is a critical-severity flaw (CVSS 9.8) affecting xmlquery. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

xmlquery before 1.3.1 lacks a check for whether a LoadURL response is in the XML format, which allows attackers to cause a denial of service (SIGSEGV) at xmlquery.(*Node).InnerText or possibly have unspecified other impact.

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.9% (top 20%)
CISA exploited list	No
Weakness	CWE-20, CWE-119
Published	2020-09-16
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: xmlquery project

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

Am I affected?

Timeline

2020-09-16 15:15 UTCPublished CVE record published
2026-06-17 03:06 UTCUpdated Record last modified

xmlquery project xmlquery UPGRADE

Affected: < 1.3.1

Fixed in: 1.3.1

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to 1.3.1 (Debian / Ubuntu)

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade xmlquery

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

xmlquery: upgrade to 1.3.1. Exact commands for each OS are on this page.

Is CVE-2020-25614 being exploited?

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

CVE-2020-25614 affects xmlquery. Severity is critical (CVSS 9.8). xmlquery before 1.3.1 lacks a check for whether a LoadURL response is in the XML format, which allows attackers to cause a denial of service (SIGSEGV) at xmlquery.(*Node).InnerText or possibly have unspecified other impact.

How urgent is CVE-2020-25614?

Priority 64/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

References

← Back to latest CVEs