How severe is CVE-2023-49652?

CVE-2023-49652 has a CVSS score of 2.7/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2023-49652?

CVE-2023-49652 affects the following packages: org.jenkins-ci.plugins:google-compute-engine (Maven), org.jenkins-ci.plugins:google-compute-engine (Maven). Ecosystems affected: Maven.

How do I fix CVE-2023-49652?

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

How do I detect CVE-2023-49652 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-compute-engine, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2023-49652 actively exploited in the wild?

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

CVE-2023-49652 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 45th 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-2023-49652?

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

When was CVE-2023-49652 published, and has it been updated?

CVE-2023-49652 was published on November 29, 2023 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

LOW severity

CVE-2023-49652 — google-compute-engine

LOW

CVE-2023-49652 is a low-severity (CVSS 2.7) CWE-862 vulnerability in org.jenkins-ci.plugins:google-compute-engine. A fix is available for org.jenkins-ci.plugins:google-compute-engine — see the affected versions and patch details below.

Jenkins Google Compute Engine Plugin has incorrect permission checks

Also known asGHSA-pgpj-83g3-mfr2

Published

Nov 29, 2023

Updated

Oct 24, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

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

2 pkgs affected

☕org.jenkins-ci.plugins:google-compute-engine☕org.jenkins-ci.plugins:google-compute-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

Enumerate system-scoped credentials IDs of credentials stored in Jenkins. Those can be used as part of an attack to capture the credentials using another vulnerability.
Connect to Google Cloud Platform using attacker-specified credentials IDs obtained through another method, to obtain information about existing projects.

Google Compute Engine Plugin 4.551.v5a_4dc98f6962 requires Overall/Administer permission for the affected HTTP endpoints.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:google-compute-engine`	all versions	4.3.17.1`org.jenkins-ci.plugins:google-compute-engine:4.3.17.1`
☕Maven	`org.jenkins-ci.plugins:google-compute-engine`	≥ 4.5&&< 4.551.v5a	4.551.v5a`org.jenkins-ci.plugins:google-compute-engine:4.551.v5a`

Affected Products

1 product · 1 configurations

Application

google compute enginejenkins

< 4.3.17.1

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-compute-engine, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:google-compute-engine to 4.3.17.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-49652 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

Jenkins Google Compute Engine Plugin 4.550.vb_327fca_3db_11 and earlier does not correctly perform permission checks in multiple HTTP endpoints. This allows attackers with global Item/Configure permission (while lacking Item/Configure permission on any particular job) to do the following: - Enumerate system-scoped credentials IDs of credentials stored in Jenkins. Those can be used as part of an attack to capture the credentials using another vulnerability. - Connect to Google Cloud Platform using attacker-specified credentials IDs obtained through another method, to obtain information about

O3 Security · Impact-Aware SCA

Is CVE-2023-49652 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

2.7/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Raw vector

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

CWE Classification

CWE-862CWE-862

Weaponization

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

Timeline

Disclosed

Nov 29, 2023

Last updated

Oct 24, 2026

Identifiers

CVE-2023-49652

GHSA-pgpj-83g3-mfr2

References

Advisoryopenwall.com Advisoryjenkins.io · 2023 11 29 Advisorynvd.nist.gov · CVE 2023 49652

Related vulnerabilities

Also affects google-compute-engine

This CVE is low severity; 4 of 4 other CVEs affecting google-compute-engine are rated as high or higher (top: moderate).

CVE-2019-16546CVE-2019-16547CVE-2019-16548CVE-2022-29052

Same weakness: CWE-862

This CVE is low severity; 4 of 4 other CVEs with CWE-862 are rated as high or higher (top: high).

CVE-2026-116677CVE-2026-116794CVE-2026-118759GHSA-w9x9-j56r-h98rBrowse all CWE-862

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2023-49652 — google-compute-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-2023-49652 in your dependencies?