How severe is CVE-2020-19676?

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

Which packages are affected by CVE-2020-19676?

CVE-2020-19676 affects the following packages: com.alibaba.nacos:nacos-common (Maven). Ecosystems affected: Maven.

How do I fix CVE-2020-19676?

Update com.alibaba.nacos:nacos-common to 1.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-19676 is resolved across your whole dependency graph.

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

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

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

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

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

Yes. There are 1 known exploit references for CVE-2020-19676, 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-2020-19676?

CVE-2020-19676 has an EPSS (Exploit Prediction Scoring System) score of 1.4%, placing it in the 72th 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.

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

CVE-2020-19676 was published on September 30, 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-19676 — nacos-common

MEDIUM

CVE-2020-19676 is a medium-severity (CVSS 5.3) vulnerability in com.alibaba.nacos:nacos-common. 1 public exploit reference exists, so weaponization risk is real. A fix is available for com.alibaba.nacos:nacos-common — see the affected versions and patch details below.

Incorrect Access Control in Nacos

Also known asGHSA-qf76-pr7x-h7r4

Published

Sep 30, 2020

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

1.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs72th percentile — riskier than 72% of all scored CVEsHighest risk

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

How urgent is this, really

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

Where this sits among everything scored

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

Real-World Exposure

1 pkg affected

☕com.alibaba.nacos:nacos-common

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

Nacos 1.1.4 is affected by: Incorrect Access Control. An environment can be set up locally to get the service details interface. Then other Nacos service names can be accessed through the service list interface. Service details can then be accessed when not logged in. (detail:https://github.com/alibaba/nacos/issues/2284)

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.alibaba.nacos:nacos-common`	all versions	1.2.0`com.alibaba.nacos:nacos-common:1.2.0`

Affected Products

1 product · 1 configurations

Application

nacosalibaba

1 version

1.1.4

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.

Nacos 1.1.4 is affected by: Incorrect Access Control. An environment can…

github.comNVDJul 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.alibaba.nacos:nacos-common, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.alibaba.nacos:nacos-common to 1.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-19676 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2020-19676 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Raw vector

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

Weaponization

No known public exploit tooling found.

OpenSSF Scorecard

Package health score

nacos

5.7/10

Maintained10/10

Code-Review4/10

Branch-ProtectionN/A

Assessed Oct 5, 2026

Timeline

Disclosed

Sep 30, 2020

First exploit

Jul 21, 2021

Last updated

Jul 8, 2026

Identifiers

CVE-2020-19676

GHSA-qf76-pr7x-h7r4

References

Advisorynvd.nist.gov Reportgithub.com Webgithub.com Webgithub.com

Related vulnerabilities

This CVE is medium severity; 3 of 3 other CVEs affecting nacos-common are rated as high or higher (top: high).

CVE-2021-44667CVE-2021-29441CVE-2021-29442

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedJul 8, 2026

CVE-2020-19676 — nacos-common

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-2020-19676 in your dependencies?