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 products are affected by CVE-2015-8103?

Affected package information for CVE-2015-8103 is not yet fully mapped. Check the official advisory links for details.

How do I patch CVE-2015-8103?

Apply the jenkins jenkins security patch or hotfix for CVE-2015-8103 on the affected version, following the vendor advisory for your exact build.

How do I detect CVE-2015-8103 across my infrastructure?

Inventory every jenkins jenkins deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for remote code execution at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

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

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2015-8103?

O3 detects and blocks CVE-2015-8103 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

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 86.8%, 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.

Which products and versions are affected by CVE-2015-8103?

CVE-2015-8103 affects jenkins jenkins; redhat openshift container platform (2 versions, e.g. 2.2, 3.1). Check the affected-products list on this page against your deployed version to confirm exposure.

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

CVE-2015-8103 was published on November 25, 2015 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2015-8103

CRITICAL

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…

Published

Nov 25, 2015

Updated

Jun 17, 2026

Affected

0 pkgs

Patched

None yet

Exploits

8 known

EPSS Exploitation Probability

via FIRST.org ↗

86.8%probability of exploitation in next 30 days

Very High Risk100th percentile+0.50%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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 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

Vendor / appliance

Detect
Inventory every jenkins jenkins deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for remote code execution at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Fix
Apply the jenkins jenkins security patch or hotfix for CVE-2015-8103 on the affected version, following the vendor advisory for your exact build.
Workarounds
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2015-8103 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2015-8103. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2015-8103 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2015-8103 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.

Protect my workloads How runtime protection works