cve.bz

CVE-2019-16546 jenkins google compute engine

5.9 mediumEPSS 0.9%Fix available

Medium (5.9) in jenkins google compute engine. EPSS 0.9% estimated probability of exploitation activity in the next 30 days. Fixed in org.jenkins-ci.plugins:google-compute-engine 4.2.0.

Jenkins Google Compute Engine Plugin 4.1.1 and earlier does not verify SSH host keys when connecting agents created by the plugin, enabling man-in-the-middle attacks.

Severity

CVSS 3.1

5.9 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.9% (unchanged from 0.9% a week ago; 0.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 60th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-639 Authorization Bypass Through User-Controlled Key
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2019-16546 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2019-16546?via=ask-ai-copy and https://cve.bz/cve/CVE-2019-16546?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2019-16546 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
jenkins:google_compute_enginebefore 4.2.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-345p-pw5q-g98vMavenorg.jenkins-ci.plugins:google-compute-engine<4.2.04.2.0

References

Check your stackJSON