How severe is CVE-2018-1000600?

CVE-2018-1000600 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2018-1000600?

CVE-2018-1000600 affects the following packages: com.coravy.hudson.plugins.github:github (Maven). Ecosystems affected: Maven.

How do I fix CVE-2018-1000600?

Update com.coravy.hudson.plugins.github:github to version 1.29.2 or later. Run your dependency manager's update command and verify no transitive dependencies pin the vulnerable version. Use O3 Security's SCA scanner to confirm the fix is applied across your entire dependency tree.

Is CVE-2018-1000600 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2018-1000600, 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-2018-1000600?

CVE-2018-1000600 has an EPSS (Exploit Prediction Scoring System) score of 93.5%, 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.

Is there exploit tooling available for CVE-2018-1000600?

A Nuclei detection template exists for CVE-2018-1000600, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2018-1000600 published, and has it been updated?

CVE-2018-1000600 was published on June 26, 2018 and was last updated on March 14, 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

CVE-2018-1000600

HIGH

CSRF vulnerability and missing permission checks in GitHub Plugin allowed capturing credentials

Also known asGHSA-6cvm-v6qj-hjq9

Published

Jun 26, 2018

Updated

Mar 14, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

93.5%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

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.

Blast Radius

1 pkg affected

☕com.coravy.hudson.plugins.github:github

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

A exposure of sensitive information vulnerability exists in Jenkins GitHub Plugin 1.29.1 and earlier in GitHubTokenCredentialsCreator.java that allows attackers to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.coravy.hudson.plugins.github:github`	all versions	1.29.2

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.

A exposure of sensitive information vulnerability exists in Jenkins GitH…

unit42.paloaltonetworks.comAPIOct 2021

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2018-1000600 in your stack?

O3 detects CVE-2018-1000600 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works