How severe is CVE-2023-46653?

CVE-2023-46653 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-46653?

CVE-2023-46653 affects the following packages: org.jenkins-ci.plugins:lambdatest-automation (Maven). Ecosystems affected: Maven.

How do I fix CVE-2023-46653?

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

How do I detect CVE-2023-46653 in my Maven dependencies?

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

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

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

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

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

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

CVE-2023-46653 was published on October 25, 2023 and was last updated on February 16, 2024. 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-46653 — lambdatest-automation

LOW

CVE-2023-46653 is a low-severity (CVSS 2.7) CWE-312 vulnerability in org.jenkins-ci.plugins:lambdatest-automation. A fix is available for org.jenkins-ci.plugins:lambdatest-automation — see the affected versions and patch details below.

Jenkins lambdatest-automation Plugin may expose Credentials access token

Published

Oct 25, 2023

Updated

Feb 16, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-46653.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs38th percentile — riskier than 38% 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:lambdatest-automation

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 lambdatest-automation Plugin 1.20.10 and earlier logs LAMBDATEST Credentials access token at the INFO level.

This can result in accidental exposure of the token through the default system log.

lambdatest-automation Plugin 1.21.0 no longer logs LAMBDATEST Credentials access token.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:lambdatest-automation`	all versions	1.21.0`org.jenkins-ci.plugins:lambdatest-automation:1.21.0`

Affected Products

1 product · 1 configurations

Application

lambdatest-automationjenkins

< 1.21.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 org.jenkins-ci.plugins:lambdatest-automation, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:lambdatest-automation to 1.21.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-46653 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 lambdatest-automation Plugin 1.20.10 and earlier logs LAMBDATEST Credentials access token at the INFO level. This can result in accidental exposure of the token through the default system log. lambdatest-automation Plugin 1.21.0 no longer logs LAMBDATEST Credentials access token.

O3 Security · Impact-Aware SCA

Is CVE-2023-46653 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-312CWE-312

Weaponization

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

Timeline

Disclosed

Oct 25, 2023

Last updated

Feb 16, 2024

Identifiers

CVE-2023-46653

References

Advisorynvd.nist.gov · CVE 2023 46653 Webjenkins.io · 2023 10 25 Webopenwall.com

Related vulnerabilities

Also affects lambdatest-automation

This CVE is low severity; 1 of 1 other CVE affecting lambdatest-automation is rated as high or higher (top: moderate).

CVE-2023-46652

Same weakness: CWE-312

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

CVE-2026-116691CVE-2026-77564CVE-2026-91982CVE-2026-107807CVE-2026-62376CVE-2026-77250CVE-2026-63406Browse all CWE-312

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedFeb 16, 2024

CVE-2023-46653 — lambdatest-automation

Exploitation Status

No confirmed exploitation observed yet

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