dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 10 Aug 2022.
JenkinsApplication

CVE-2018-1000861

CRITICAL · 9.8 CVSS v3.1 Published 2018-12-10
Fix available
A fix is available. Upgrade to after 2.153 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A code execution vulnerability exists in the Stapler web framework used by Jenkins 2.153 and earlier, LTS 2.138.3 and earlier in stapler/core/src/main/java/org/kohsuke/stapler/MetaClass.java that allows attackers to invoke some methods on Java objects by accessing crafted URLs that were not intended to be invoked this way.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A code execution vulnerability in the Stapler web framework (used by Jenkins 2.153 and earlier and LTS 2.138.3 and earlier) allows attackers to invoke arbitrary methods on Java objects via crafted URLs that were not intended to be exposed, leading to remote code execution.

MitigationUpgrade to Jenkins 2.154 or LTS 2.138.4 or later which contain the patch for this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JenkinsApplication
Affected:<= 2.138.3<= 2.153
Openshift Container PlatformApplication
Affected:= 3.11

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Jenkins version
    Run 'java -jar jenkins.war --version' if using WAR file, or check the Jenkins UI footer which displays the version number, or query the Jenkins API endpoint: curl -s http://TARGET:8080/api/json?tree=version
    Affected if Version is 2.138.3 or lower, OR between 2.139.0 and 2.153 (inclusive)
  2. Confirm Jenkins HTTP interface is accessible
    Attempt to reach the Jenkins UI: curl -s -o /dev/null -w '%{http_code}' http://TARGET:8080/ or https://TARGET:8443/
    Affected if HTTP/HTTPS response returns 200 or 403, indicating Jenkins is network-reachable (this exposes the Stapler framework to potential attack)
  3. Check if Stapler endpoint is reachable
    Probe a known Stapler route that triggers the vulnerable code path, such as: curl -s http://TARGET:8080/adjuncts/ or other meta-URLs that exercise MetaClass.java routing
    Affected if Any Stapler route returns a response, confirming the framework is active and potentially exploitable
  4. For OpenShift environments, verify Jenkins pod status
    Run 'oc get pods -l app=jenkins -o jsonpath={.items[*].spec.containers[*].image}' to identify the Jenkins image version in use
    Affected if Image version corresponds to an affected Jenkins version (2.138.3 or lower, or 2.153 or lower)

You are affected if Jenkins is accessible over HTTP/HTTPS and the installed version falls within 2.0 through 2.138.3, or 2.139.0 through 2.153.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2.153
Interim mitigation

Upgrade to Jenkins 2.154 or LTS 2.138.4 or later which contain the patch for this vulnerability.

Recommended fix High confidence

Jenkins LTS 2.138.4 or later (LTS), Jenkins 2.154 or later (weekly)

  1. Identify the current Jenkins version by navigating to Manage Jenkins > About Jenkins
  2. Verify if the version is <= 2.138.3 (LTS) or <= 2.153 (weekly) - both are vulnerable
  3. Determine whether you are on the LTS or weekly release train
  4. For LTS users: Plan upgrade to Jenkins 2.138.4 or later
  5. For weekly users: Plan upgrade to Jenkins 2.154 or later
  6. Review Jenkins upgrade documentation and release notes for compatibility notes
  7. Test the upgrade in a non-production environment before deploying to production
  8. Perform a full backup of Jenkins home directory and configuration
Caveat Review release notes for any plugin compatibility or configuration changes between versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jenkins Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1000861 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-1000861 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data