How severe is CVE-2016-2510?

CVE-2016-2510 has a CVSS score of 8.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2016-2510?

CVE-2016-2510 affects the following packages: org.apache-extras.beanshell:bsh (Maven). Ecosystems affected: Maven.

How do I fix CVE-2016-2510?

Update org.apache-extras.beanshell:bsh to 2.0b6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-2510 is resolved across your whole dependency graph.

How do I detect CVE-2016-2510 in my Maven dependencies?

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

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

Yes. There are 2 known exploit references for CVE-2016-2510, including 2 in-the-wild exploitations 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-2016-2510?

CVE-2016-2510 has an EPSS (Exploit Prediction Scoring System) score of 70.4%, placing it in the 99th 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. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2016-2510?

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

When was CVE-2016-2510 published, and has it been updated?

CVE-2016-2510 was published on April 7, 2016 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.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2016-2510 — bsh

HIGHFix: beanshell/beanshell@1ccc66b

CVE-2016-2510 is a high-severity (CVSS 8.1) CWE-19 vulnerability in org.apache-extras.beanshell:bsh. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.apache-extras.beanshell:bsh — see the affected versions and patch details below.

Improper Input Validation in BeanShell

Also known asGHSA-gxg6-rc6c-v673

Published

Apr 7, 2016

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

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

EPSS Exploitation Probability

via FIRST.org ↗

70.4%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs99th percentile — riskier than 99% 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.apache-extras.beanshell:bsh

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

BeanShell (bsh) before 2.0b6, when included on the classpath by an application that uses Java serialization or XStream, allows remote attackers to execute arbitrary code via crafted serialized data, related to XThis.Handler.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache-extras.beanshell:bsh`	all versions	2.0b6`org.apache-extras.beanshell:bsh:2.0b6`

Affected Products

3 products · 9 configurations

Application

beanshellbeanshell

2 versions

1.02.0

ubuntu linuxcanonical

3 versions

12.0414.0415.10

debian linuxdebian

2 versions

7.08.0

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.

BeanShell (bsh) before 2.0b6, when included on the classpath by an appli…

rsaconference.comNVDOct 2020

Report on github.com

github.comNVDOct 2020

Detection & mitigation playbook

Open-source dependency

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

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 HatImportant

Product	Fixed in	Advisory
Red Hat Fuse 7.3.1	`camel`	RHSA-2019:1545
Red Hat JBoss BPMS 6.2	see advisory	RHSA-2016:0539
Red Hat JBoss BRMS 6.2	see advisory	RHSA-2016:0540
Red Hat JBoss Data Virtualization 6.2	`bsh2`	RHSA-2016:1135
Red Hat JBoss Fuse 6.3	see advisory	RHSA-2016:2035
Red Hat JBoss SOA Platform 5.3	`jbossas`	RHSA-2016:1376

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2016-2510 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works