How severe is CVE-2019-10365?

CVE-2019-10365 has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2019-10365?

CVE-2019-10365 affects the following packages: org.jenkins-ci.plugins:google-kubernetes-engine (Maven). Ecosystems affected: Maven.

How do I fix CVE-2019-10365?

Update org.jenkins-ci.plugins:google-kubernetes-engine to 0.6.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-10365 is resolved across your whole dependency graph.

How do I detect CVE-2019-10365 in my Maven dependencies?

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

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

No public exploit code has been indexed for CVE-2019-10365 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-2019-10365?

CVE-2019-10365 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 28th 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-2019-10365?

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

When was CVE-2019-10365 published, and has it been updated?

CVE-2019-10365 was published on July 31, 2019 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-2019-10365 — google-kubernetes-engine

MEDIUM

CVE-2019-10365 is a medium-severity (CVSS 4.3) CWE-668 vulnerability in org.jenkins-ci.plugins:google-kubernetes-engine. A fix is available for org.jenkins-ci.plugins:google-kubernetes-engine — see the affected versions and patch details below.

Jenkins Google Kubernetes Engine Plugin vulnerable to Exposure of Resource to Wrong Sphere

Also known asGHSA-xw4c-9434-3f7p

Published

Jul 31, 2019

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

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

☕org.jenkins-ci.plugins:google-kubernetes-engine

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

Jenkins Google Kubernetes Engine Plugin 0.6.2 and earlier created a temporary file named .kube…config containing a temporary access token in the project workspace, where it could be accessed by users with Job/Read permission.

This temporary file is now created outside the regular project workspace.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:google-kubernetes-engine`	all versions	0.6.3`org.jenkins-ci.plugins:google-kubernetes-engine:0.6.3`

Affected Products

1 product · 1 configurations

Application

kubernetes enginegoogle

≤ 0.6.2

range

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.plugins:google-kubernetes-engine, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:google-kubernetes-engine to 0.6.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-10365 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.

Frequently Asked Questions

Jenkins Google Kubernetes Engine Plugin 0.6.2 and earlier created a temporary file named `.kube…config` containing a temporary access token in the project workspace, where it could be accessed by users with Job/Read permission. This temporary file is now created outside the regular project workspace.

O3 Security · Impact-Aware SCA

Is CVE-2019-10365 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

4.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Raw vector

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

CWE Classification

CWE-668CWE-668

Weaponization

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

Timeline

Disclosed

Jul 31, 2019

Last updated

Oct 24, 2026

Identifiers

CVE-2019-10365

GHSA-xw4c-9434-3f7p

References

Advisoryopenwall.com Advisoryjenkins.io · 2019 07 31 Advisorynvd.nist.gov · CVE 2019 10365

Related vulnerabilities

Also affects google-kubernetes-engine

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

CVE-2020-2121CVE-2019-10445

Same weakness: CWE-668

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

CVE-2026-112936CVE-2026-62204CVE-2026-92947CVE-2026-105754CVE-2026-92940CVE-2026-61590Browse all CWE-668

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2019-10365 — google-kubernetes-engine

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-2019-10365 in your dependencies?