How severe is CVE-2015-8103?

CVE-2015-8103 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2015-8103?

CVE-2015-8103 affects the following packages: org.jenkins-ci.main:cli (Maven), org.jenkins-ci.main:cli (Maven). Ecosystems affected: Maven.

How do I fix CVE-2015-8103?

Update org.jenkins-ci.main:cli to 1.625.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-8103 is resolved across your whole dependency graph.

How do I detect CVE-2015-8103 in my Maven dependencies?

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

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

Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Is CVE-2015-8103 actively exploited in the wild?

Yes. There are 8 known exploit references for CVE-2015-8103, including 1 documented proof-of-concept exploit on Exploit-DB and 7 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-2015-8103?

CVE-2015-8103 has an EPSS (Exploit Prediction Scoring System) score of 91.9%, placing it in the 100th 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-2015-8103?

CVE-2015-8103 is classified as Deserialization of Untrusted Data (CWE-502). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2015-8103 published, and has it been updated?

CVE-2015-8103 was published on May 13, 2022 and was last updated on March 4, 2024. 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

CRITICAL severity

CVE-2015-8103 — cli

CRITICALFix: jenkinsci/jenkins@5bd9b55

CVE-2015-8103 is a critical-severity (CVSS 9.8) Deserialization of Untrusted Data vulnerability in org.jenkins-ci.main:cli. 8 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.jenkins-ci.main:cli — see the affected versions and patch details below.

Jenkins CLI Deserialization of Untrusted Data vulnerability

Published

May 13, 2022

Updated

Mar 4, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

8 known

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

EPSS Exploitation Probability

via FIRST.org ↗

91.9%probability of exploitation in next 30 days

Very High Risk0.00%

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

2 pkgs affected

☕org.jenkins-ci.main:cli☕org.jenkins-ci.main:cli

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

The Jenkins CLI subsystem in Jenkins before 1.638 and LTS before 1.625.2 allows remote attackers to execute arbitrary code via a crafted serialized Java object, related to a problematic webapps/ROOT/WEB-INF/lib/commons-collections-*.jar file and the "Groovy variant in ysoserial".

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.main:cli`	all versions	1.625.2`org.jenkins-ci.main:cli:1.625.2`
☕Maven	`org.jenkins-ci.main:cli`	≥ 1.626&&< 1.638	1.638`org.jenkins-ci.main:cli:1.638`

Affected Products

2 products · 4 configurations

Application

jenkinsjenkins

< 1.638

range

Application

openshift container platformredhat

2 versions

2.23.1

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.

EDB-38983remotejava✓ Verified

Jenkins CLI - RMI Java Deserialization (Metasploit)

by Metasploit · Dec 15, 2015

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.main:cli, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.main:cli to 1.625.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-8103 is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

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

Workaround published by Red Hat

https://jenkins-ci.org/content/mitigating-unauthenticated-remote-code-execution-0-day-jenkins-cli

Source: Red Hat security advisory for CVE-2015-8103 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat OpenShift Enterprise 2.2	`activemq-0:5.9.0-6.redhat.611454.el6op`	RHSA-2016:0489
Red Hat OpenShift Enterprise 3.1	`atomic-openshift-0:3.1.1.6-1.git.0.b57e8bd.el7aos`	RHSA-2016:0070

Frequently Asked Questions

The Jenkins CLI subsystem in Jenkins before 1.638 and LTS before 1.625.2 allows remote attackers to execute arbitrary code via a crafted serialized Java object, related to a problematic `webapps/ROOT/WEB-INF/lib/commons-collections-*.jar` file and the "Groovy variant in `ysoserial`".

O3 Security · Impact-Aware SCA

Is CVE-2015-8103 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

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

CWE Classification

CWE-502Deserialization of Untrusted Data

Weaponization

No Nuclei template or Metasploit module yet. 8 public proof-of-concept references are listed on this page.

OpenSSF Scorecard

Package health score

jenkins

6.4/10

Code-Review6/10

Maintained10/10

Branch-Protection3/10

Assessed Oct 26, 2026

Timeline

First exploit

Dec 15, 2015

Disclosed

May 13, 2022

Last updated

Mar 4, 2024

Identifiers

CVE-2015-8103

References

Advisorynvd.nist.gov · CVE 2015 8103 Webgithub.com · 5bd9b55a2a3249939fd78c501b8959a804c1164b Webgithub.com · b4193d1132089286ebeaf9d8872c839ad473329c Webaccess.redhat.com · RHSA 2016:0070 Webjenkins-ci.org · mitigating unauthenticated remote code execution 0 day jenkins cli Webweb.archive.org Webwiki.jenkins-ci.org · Jenkins+Security+Advisory+2015 11 11 Webexploit-db.com Webfoxglovesecurity.com · what do weblogic websphere jboss jenkins opennms and your application have in common this vulnerability Webpacketstormsecurity.com · Jenkins CLI RMI Java Deserialization Webrhn.redhat.com · RHSA 2016 0489 Webopenwall.com Webopenwall.com Webopenwall.com Webopenwall.com Packagegithub.com · jenkins

Related vulnerabilities

Also affects cli

This CVE is critical severity — higher than any of the other 1 CVE affecting cli (highest there: high).

CVE-2025-67635

Same weakness: CWE-502

This CVE is critical severity; 1 of 7 other CVEs with CWE-502 is rated as high or higher (top: critical).

CVE-2026-115878CVE-2026-62848CVE-2026-115912CVE-2026-116580CVE-2026-114608CVE-2026-102554GHSA-673q-mjm6-r5xrBrowse all CWE-502

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedMar 4, 2024

CVE-2015-8103 — cli

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