How severe is CVE-2016-9299?

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

Which packages are affected by CVE-2016-9299?

CVE-2016-9299 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-9299?

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

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

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

CVE-2016-9299 has an EPSS (Exploit Prediction Scoring System) score of 96.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-2016-9299?

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

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

CVE-2016-9299 was published on January 12, 2017 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-9299 — jenkins-core

CRITICALFix: jenkinsci/jenkins@6078dd7

CVE-2016-9299 is a critical-severity (CVSS 9.8) CWE-90 vulnerability in org.jenkins-ci.main:jenkins-core. 2 public exploit references exist, so weaponization risk is real. A fix is available for org.jenkins-ci.main:jenkins-core — see the affected versions and patch details below.

Improper Neutralization of Special Elements used in an LDAP Query in Jenkins

Also known asGHSA-2x9h-h3c4-wqqh

Published

Jan 12, 2017

Updated

Oct 24, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

2 known

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

EPSS Exploitation Probability

via FIRST.org ↗

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

CVE-2016-9299 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).

Where this sits among everything scored

Of 396,966 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.

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 2.32 and LTS before 2.19.3 allows remote attackers to execute arbitrary code via a crafted serialized Java object, which triggers an LDAP query to a third-party server.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.main:jenkins-core`	≥ 2.20&&< 2.32	2.32`org.jenkins-ci.main:jenkins-core:2.32`
☕Maven	`org.jenkins-ci.main:jenkins-core`	all versions	2.19.3`org.jenkins-ci.main:jenkins-core:2.19.3`

Affected Products

2 products · 3 configurations

fedorafedoraproject

1 version

Application

jenkinsjenkins

≤ 2.31

range

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-44642remotelinux✓ Verified

Jenkins CLI - HTTP Java Deserialization (Metasploit)

by Metasploit · May 17, 2018

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: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 2.32 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-9299 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

Workaround published by Red Hat

https://github.com/jenkinsci-cert/SECURITY-218

Source: Red Hat security advisory for CVE-2016-9299 (CC BY 4.0)

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2016-9299 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-90CWE-90

Weaponization

No known public exploit tooling found.

OpenSSF Scorecard

Package health score

jenkins

6.4/10

Code-Review6/10

Maintained10/10

Branch-Protection3/10

Assessed Oct 26, 2026

Timeline

Disclosed

Jan 12, 2017

First exploit

May 17, 2018

Last updated

Oct 24, 2026

Identifiers

CVE-2016-9299

GHSA-2x9h-h3c4-wqqh

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