How severe is CVE-2016-0788?

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

Which packages are affected by CVE-2016-0788?

CVE-2016-0788 affects the following packages: org.jenkins-ci.main:jenkins-core (Maven), org.jenkins-ci.main:jenkins-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2016-0788?

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

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

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

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

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

CVE-2016-0788 has an EPSS (Exploit Prediction Scoring System) score of 11.8%, placing it in the 96th 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 warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2016-0788?

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

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

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

CRITICAL severity

CVE-2016-0788 — jenkins-core

CRITICALFix: jenkinsci/jenkins@1ec232c

CVE-2016-0788 is a critical-severity (CVSS 9.8) CWE-264 vulnerability in org.jenkins-ci.main:jenkins-core. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.jenkins-ci.main:jenkins-core — see the affected versions and patch details below.

Jenkins allows Execution of Code by Opening a JRMP Listener

Also known asGHSA-j7q5-h445-f7pc

Published

Apr 7, 2016

Updated

Oct 24, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

2 known

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

EPSS Exploitation Probability

via FIRST.org ↗

11.8%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs96th percentile — riskier than 96% 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:jenkins-core☕org.jenkins-ci.main:jenkins-core

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 remoting module in Jenkins before 1.650 and LTS before 1.642.2 allows remote attackers to execute arbitrary code by opening a JRMP listener.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.main:jenkins-core`	≥ 1.643&&< 1.650	1.650`org.jenkins-ci.main:jenkins-core:1.650`
☕Maven	`org.jenkins-ci.main:jenkins-core`	all versions	1.642.2`org.jenkins-ci.main:jenkins-core:1.642.2`

Affected Products

2 products · 3 configurations

Application

jenkinsjenkins

≤ 1.649

1 version

1.642.1

Application

openshiftredhat

1 version

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

The remoting module in Jenkins before 1.650 and LTS before 1.642.2 allow…

blog.csdn.netAwesomePocJun 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.jenkins-ci.main:jenkins-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.main:jenkins-core to 1.650 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-0788 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 OpenShift Enterprise 2.2	`activemq-0:5.9.0-6.redhat.611463.el6op`	RHSA-2016:1773
Red Hat OpenShift Enterprise 3.1	`jenkins-0:1.642.2-1.el7`	RHSA-2016:0711

Frequently Asked Questions

The remoting module in Jenkins before 1.650 and LTS before 1.642.2 allows remote attackers to execute arbitrary code by opening a JRMP listener.

O3 Security · Impact-Aware SCA

Is CVE-2016-0788 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.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CWE Classification

CWE-264CWE-264

Weaponization

No Nuclei template or Metasploit module yet. 2 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

Disclosed

Apr 7, 2016

First exploit

Jun 26, 2020

Last updated

Oct 24, 2026

Identifiers

CVE-2016-0788

GHSA-j7q5-h445-f7pc

References

Advisoryrhn.redhat.com · RHSA 2016 1773 Advisoryaccess.redhat.com · RHSA 2016:0711 Advisorynvd.nist.gov · CVE 2016 0788 Fixwiki.jenkins-ci.org · Jenkins+Security+Advisory+2016 02 24 Webgithub.com · 1ec232ca1c80e924d70212313b852aec408aa37e Packagegithub.com · jenkins

Related vulnerabilities

This CVE is critical severity — higher than any of the other 8 CVEs affecting jenkins-core (highest there: high).

CVE-2026-53436CVE-2026-53437CVE-2026-53440CVE-2026-53441CVE-2026-53439CVE-2026-53435CVE-2026-53442CVE-2026-53438

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2016-0788 — jenkins-core

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