How severe is CVE-2019-20627?

CVE-2019-20627 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-20627?

CVE-2019-20627 affects the following packages: Autoupdater.NET.Official (NuGet). Ecosystems affected: NuGet.

How do I fix CVE-2019-20627?

Update Autoupdater.NET.Official to 1.5.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-20627 is resolved across your whole dependency graph.

How do I detect CVE-2019-20627 in my NuGet dependencies?

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

How do I mitigate CVE-2019-20627 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-2019-20627 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2019-20627, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2019-20627?

CVE-2019-20627 has an EPSS (Exploit Prediction Scoring System) score of 2.3%, placing it in the 84th 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-2019-20627?

CVE-2019-20627 is classified as XML External Entity (XXE) (CWE-611). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2019-20627 published, and has it been updated?

CVE-2019-20627 was published on March 23, 2020 and was last updated on October 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET

.NET NuGet

Not in CISA KEV

CRITICAL severity

CVE-2019-20627 — Autoupdater.NET.Official

CRITICALFix: ravibpatel/AutoUpdater.NET@1dc25f2

CVE-2019-20627 is a critical-severity (CVSS 9.8) XML External Entity (XXE) vulnerability in Autoupdater.NET.Official. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for Autoupdater.NET.Official — see the affected versions and patch details below.

AutoUpdater.NET allows XXE

Also known asGHSA-75p2-hgw4-g7f7

Published

Mar 23, 2020

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

2.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs84th percentile — riskier than 84% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

.NETAutoupdater.NET.Official

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

Description

AutoUpdater.cs in AutoUpdater.NET before 1.5.8 allows XXE.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`Autoupdater.NET.Official`	all versions	1.5.8`dotnet add package Autoupdater.NET.Official --version 1.5.8`

Affected Products

1 product · 1 configurations

Application

autoupdater.netrbsoft

< 1.5.8

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

AutoUpdater.cs in AutoUpdater.NET before 1.5.8 allows XXE.

doyler.netNVDFeb 2023

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Autoupdater.NET.Official, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update Autoupdater.NET.Official to 1.5.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-20627 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.

Frequently Asked Questions

AutoUpdater.cs in AutoUpdater.NET before 1.5.8 allows XXE.

O3 Security · Impact-Aware SCA

Is CVE-2019-20627 in your dependencies?

Find it across NuGet, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CWE Classification

CWE-611XML External Entity (XXE)

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

OpenSSF Scorecard

Package health score

AutoUpdater.NET

1.7/10

Maintained0/10

Code-Review0/10

Branch-Protection0/10

Assessed Oct 26, 2026

Timeline

Disclosed

Mar 23, 2020

First exploit

Feb 3, 2023

Last updated

Oct 20, 2026

Identifiers

CVE-2019-20627

GHSA-75p2-hgw4-g7f7

References

Advisorygithub.com · v1.5.8 Advisorynvd.nist.gov · CVE 2019 20627 Fixgithub.com · 1dc25f2bea6ea522dbac1512b5563c4746d539c3 Packagegithub.com · AutoUpdater.NET Evidencedoyler.net · autoupdater net vulnerability

Related vulnerabilities

This CVE is critical severity; 1 of 8 other CVEs with CWE-611 is rated as high or higher (top: critical).

CVE-2026-108358CVE-2026-108357CVE-2026-61586CVE-2026-61741CVE-2026-61570CVE-2026-55848CVE-2026-54079CVE-2026-54078Browse all CWE-611

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 20, 2026

CVE-2019-20627 — Autoupdater.NET.Official

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

Frequently Asked Questions

Is CVE-2019-20627 in your dependencies?