How severe is CVE-2021-20250?

CVE-2021-20250 has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2021-20250?

CVE-2021-20250 affects the following packages: org.jboss:jboss-ejb-client (Maven). Ecosystems affected: Maven.

How do I fix CVE-2021-20250?

Update org.jboss:jboss-ejb-client to 4.0.39 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-20250 is resolved across your whole dependency graph.

How do I detect CVE-2021-20250 in my Maven dependencies?

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

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

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2021-20250 actively exploited in the wild?

No public exploit code has been indexed for CVE-2021-20250 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-2021-20250?

CVE-2021-20250 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 55th 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-2021-20250?

CVE-2021-20250 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2021-20250 published, and has it been updated?

CVE-2021-20250 was published on May 13, 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-2021-20250 — jboss-ejb-client

MEDIUM

CVE-2021-20250 is a medium-severity (CVSS 4.3) Information Exposure vulnerability in org.jboss:jboss-ejb-client. A fix is available for org.jboss:jboss-ejb-client — see the affected versions and patch details below.

JBoss EJB Client information disclosure vulnerability

Also known asGHSA-2259-h742-5vr4

Published

May 13, 2021

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

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

☕org.jboss:jboss-ejb-client

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 wildfly. The JBoss EJB client has publicly accessible privileged actions which may lead to information disclosure on the server it is deployed on. The highest threat from this vulnerability is to data confidentiality.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jboss:jboss-ejb-client`	all versions	4.0.39`org.jboss:jboss-ejb-client:4.0.39`

Affected Products

2 products · 2 configurations

Application

jboss enterprise application platform expansion packredhat

all

Application

jboss-ejb-clientredhat

< 4.0.39

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jboss:jboss-ejb-client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jboss:jboss-ejb-client to 4.0.39 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-20250 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

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 HatModerate

Product	Fixed in	Advisory
Red Hat EAP-XP 2.0.0 via EAP 7.3.x base	`jboss-ejb-client`	RHSA-2021:2755
Red Hat EAP-XP via EAP 7.3.x base	`jboss-ejb-client`	RHSA-2021:2210
Red Hat JBoss Enterprise Application Platform 7	`jboss-ejb-client`	RHSA-2021:0885
Red Hat JBoss Enterprise Application Platform 7.3 for RHEL 6	`eap7-activemq-artemis-0:2.9.0-9.redhat_00019.1.el6eap`	RHSA-2021:0872
Red Hat JBoss Enterprise Application Platform 7.3 for RHEL 7	`eap7-activemq-artemis-0:2.9.0-9.redhat_00019.1.el7eap`	RHSA-2021:0873
Red Hat JBoss Enterprise Application Platform 7.3 for RHEL 8	`eap7-activemq-artemis-0:2.9.0-9.redhat_00019.1.el8eap`	RHSA-2021:0874
Red Hat Single Sign-On 7.4.6	`jboss-ejb-client`	RHSA-2021:0974

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2021-20250 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

4.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Raw vector

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

CWE Classification

CWE-200Information Exposure

Weaponization

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

Timeline

Disclosed

May 13, 2021

Last updated

Oct 24, 2026

Identifiers

CVE-2021-20250

GHSA-2259-h742-5vr4

References

Advisorynvd.nist.gov · CVE 2021 20250 Reportbugzilla.redhat.com · show bug.cgi

Related vulnerabilities

Also affects jboss-ejb-client

This CVE is medium severity, in line with the other 1 CVE affecting jboss-ejb-client.

CVE-2020-14297

Same weakness: CWE-200

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

CVE-2026-123372CVE-2026-123796CVE-2026-55098GHSA-m3qr-fvp4-78xjCVE-2026-119199CVE-2026-118759CVE-2026-62264Browse all CWE-200

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2021-20250 — jboss-ejb-client

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-2021-20250 in your dependencies?