How severe is CVE-2018-1000190?

CVE-2018-1000190 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2018-1000190?

CVE-2018-1000190 affects the following packages: com.blackducksoftware.integration:blackduck-hub (Maven). Ecosystems affected: Maven.

How do I fix CVE-2018-1000190?

Update com.blackducksoftware.integration:blackduck-hub to 4.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-1000190 is resolved across your whole dependency graph.

How do I detect CVE-2018-1000190 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.blackducksoftware.integration:blackduck-hub, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

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

No public exploit code has been indexed for CVE-2018-1000190 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2018-1000190?

CVE-2018-1000190 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 63th 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 indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2018-1000190?

CVE-2018-1000190 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2018-1000190 was published on June 5, 2018 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

MEDIUM severity

CVE-2018-1000190 — blackduck-hub

MEDIUM

CVE-2018-1000190 is a medium-severity (CVSS 6.5) Information Exposure vulnerability in com.blackducksoftware.integration:blackduck-hub. A fix is available for com.blackducksoftware.integration:blackduck-hub — see the affected versions and patch details below.

Exposure of sensitive information vulnerability in Jenkins Black Duck Hub Plugin

Also known asGHSA-26hw-262c-g9gc

Published

Jun 5, 2018

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs63th percentile — riskier than 63% 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

1 pkg affected

☕com.blackducksoftware.integration:blackduck-hub

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 Black Duck Hub Plugin 4.0.0 and older in PostBuildScanDescriptor.java that allows attackers with Overall/Read access to connect 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.blackducksoftware.integration:blackduck-hub`	all versions	4.0.1`com.blackducksoftware.integration:blackduck-hub:4.0.1`

Affected Products

1 product · 1 configurations

Application

black duck hubjenkins

≤ 4.0.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.blackducksoftware.integration:blackduck-hub, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.blackducksoftware.integration:blackduck-hub to 4.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-1000190 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2018-1000190 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

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

CWE Classification

CWE-200Information Exposure

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Jun 5, 2018

Last updated

Oct 24, 2026

Identifiers

CVE-2018-1000190

GHSA-26hw-262c-g9gc

References

Advisoryjenkins.io · 2018 06 04 Advisorynvd.nist.gov · CVE 2018 1000190

Related vulnerabilities

Also affects blackduck-hub

This CVE is medium severity; 2 of 2 other CVEs affecting blackduck-hub are rated as high or higher (top: high).

CVE-2018-1000198CVE-2018-1000197

Same weakness: CWE-200

This CVE is medium severity; 5 of 6 other CVEs with CWE-200 are rated as high or higher (top: high).

CVE-2026-55098GHSA-m3qr-fvp4-78xjCVE-2026-119199CVE-2026-118759CVE-2026-62264GHSA-473q-m89c-ghf8Browse all CWE-200

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2018-1000190 — blackduck-hub

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

Frequently Asked Questions

Is CVE-2018-1000190 in your dependencies?