How severe is CVE-2020-1729?

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

Which packages are affected by CVE-2020-1729?

CVE-2020-1729 affects the following packages: io.smallrye.config:smallrye-config (Maven). Ecosystems affected: Maven.

How do I fix CVE-2020-1729?

Update io.smallrye.config:smallrye-config to 1.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-1729 is resolved across your whole dependency graph.

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

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

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

No public exploit code has been indexed for CVE-2020-1729 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2020-1729?

CVE-2020-1729 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 19th 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-2020-1729?

CVE-2020-1729 is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2020-1729 was published on May 28, 2021 and was last updated on October 24, 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-1729 — smallrye-config

MEDIUMFix: smallrye/smallrye-config@fb0def6

CVE-2020-1729 is a medium-severity (CVSS 4.4) CWE-863 vulnerability in io.smallrye.config:smallrye-config. A fix is available for io.smallrye.config:smallrye-config — see the affected versions and patch details below.

Permissions bypass in SmallRye

Also known asGHSA-54fx-gm74-q676

Published

May 28, 2021

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs19th percentile — riskier than 19% 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

☕io.smallrye.config:smallrye-config

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

A flaw was found in SmallRye's API through version 1.6.1. The API can allow other code running within the application server to potentially obtain the ClassLoader, bypassing any permissions checks that should have been applied. The largest threat from this vulnerability is a threat to data confidentiality. This is fixed in SmallRye 1.6.2

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.smallrye.config:smallrye-config`	all versions	1.6.2`io.smallrye.config:smallrye-config:1.6.2`

Affected Products

1 product · 1 configurations

Application

smallrye configredhat

< 1.6.2

range

Detection & mitigation playbook

Open-source dependency

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

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatLow

Product	Fixed in	Advisory
Red Hat JBoss EAP 7.2	`smallrye-config`	RHSA-2020:2061
Red Hat JBoss Enterprise Application Platform 7	`smallrye-config`	RHSA-2020:2515
Red Hat JBoss Enterprise Application Platform 7.2 for RHEL 6	`eap7-activemq-artemis-0:2.9.0-4.redhat_00010.1.el6eap`	RHSA-2020:2058
Red Hat JBoss Enterprise Application Platform 7.2 for RHEL 7	`eap7-activemq-artemis-0:2.9.0-4.redhat_00010.1.el7eap`	RHSA-2020:2059
Red Hat JBoss Enterprise Application Platform 7.2 for RHEL 8	`eap7-activemq-artemis-0:2.9.0-4.redhat_00010.1.el8eap`	RHSA-2020:2060
Red Hat JBoss Enterprise Application Platform 7.3 for RHEL 6	`eap7-activemq-artemis-0:2.9.0-4.redhat_00010.1.el6eap`	RHSA-2020:2511
Red Hat JBoss Enterprise Application Platform 7.3 for RHEL 7	`eap7-activemq-artemis-0:2.9.0-4.redhat_00010.1.el7eap`	RHSA-2020:2512
Red Hat JBoss Enterprise Application Platform 7.3 for RHEL 8	`eap7-activemq-artemis-0:2.9.0-4.redhat_00010.1.el8eap`	RHSA-2020:2513

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2020-1729 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

4.4/10CVSS v3 base

Vector breakdown

Attack Vector

Local

Attack Complexity

Low

Privileges Required

High

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

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

CWE Classification

CWE-863CWE-863

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

smallrye-config

4.4/10

Code-Review2/10

Maintained10/10

Branch-Protection8/10

Assessed Oct 26, 2026

Timeline

Disclosed

May 28, 2021

Last updated

Oct 24, 2026

Identifiers

CVE-2020-1729

GHSA-54fx-gm74-q676

References

Advisorynvd.nist.gov · CVE 2020 1729 Fixbugzilla.redhat.com · show bug.cgi Webgithub.com · fb0def6f61c09a2a80c9145e4ec6521225cd0b99

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs with CWE-863 are rated as high or higher (top: high).

CVE-2026-63198CVE-2026-88984CVE-2026-62662CVE-2026-55098GHSA-j656-3hf2-fvjcCVE-2026-118669CVE-2026-119200GHSA-fgxm-5hvv-x4vhBrowse all CWE-863

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2020-1729 — smallrye-config

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

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2020-1729 in your dependencies?