How severe is CVE-2020-35510?

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

Which packages are affected by CVE-2020-35510?

CVE-2020-35510 affects the following packages: org.jboss.remoting:jboss-remoting (Maven). Ecosystems affected: Maven.

How do I fix CVE-2020-35510?

Update org.jboss.remoting:jboss-remoting to 5.0.20.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-35510 is resolved across your whole dependency graph.

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

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

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

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

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

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

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

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

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

CVE-2020-35510 was published on June 2, 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-35510 — jboss-remoting

MEDIUM

CVE-2020-35510 is a medium-severity (CVSS 5.9) Uncontrolled Resource Consumption vulnerability in org.jboss.remoting:jboss-remoting. A fix is available for org.jboss.remoting:jboss-remoting — see the affected versions and patch details below.

Uncontrolled Resource Consumption in jboss-remoting

Also known asGHSA-p6j8-hgv5-m35g

Published

Jun 2, 2021

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs65th percentile — riskier than 65% 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.remoting:jboss-remoting

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 jboss-remoting in versions before 5.0.20.SP1-redhat-00001. A malicious attacker could cause threads to hold up forever in the EJB server by writing a sequence of bytes corresponding to the expected messages of a successful EJB client request, but omitting the ACK messages, or just tamper with jboss-remoting code, deleting the lines that send the ACK message from the EJB client code resulting in a denial of service. The highest threat from this vulnerability is to system availability.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jboss.remoting:jboss-remoting`	all versions	5.0.20.Final`org.jboss.remoting:jboss-remoting:5.0.20.Final`

Affected Products

1 product · 2 configurations

Application

jboss-remotingredhat

< 5.0.20

1 version

5.0.20

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.remoting:jboss-remoting, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jboss.remoting:jboss-remoting to 5.0.20.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-35510 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

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 via EAP 7.3.x base	`jboss-remoting`	RHSA-2021:2210
Red Hat Fuse 7.10	`jboss-remoting`	RHSA-2021:5134
Red Hat JBoss Enterprise Application Platform 7	`jboss-remoting`	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-remoting`	RHSA-2021:0974

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2020-35510 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.9/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Raw vector

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

CWE Classification

CWE-400Uncontrolled Resource Consumption

Weaponization

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

Timeline

Disclosed

Jun 2, 2021

Last updated

Oct 24, 2026

Identifiers

CVE-2020-35510

GHSA-p6j8-hgv5-m35g

References

Advisorynvd.nist.gov · CVE 2020 35510 Reportbugzilla.redhat.com · show bug.cgi

Related vulnerabilities

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

CVE-2026-118773CVE-2026-119206CVE-2026-119207CVE-2026-119208CVE-2026-118779CVE-2026-119284CVE-2026-119204CVE-2026-116774Browse all CWE-400

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2020-35510 — jboss-remoting

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