Jenkins OpenTelemetry Plugin missing permission check allows capturing credentialsGHSA-f696-867g-2759
MEDIUMFix: jenkinsci/opentelemetry-plugin@f5a4ec1GHSA-f696-867g-2759 is a medium-severity (CVSS 4.2) CWE-862 vulnerability in io.jenkins.plugins:opentelemetry. A fix is available for io.jenkins.plugins:opentelemetry — see the affected versions and patch details below.
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 GHSA-f696-867g-2759.
EPSS Exploitation Probability
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
io.jenkins.plugins:opentelemetryReal-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 missing permission check in Jenkins OpenTelemetry Plugin 3.1543.v8446b_92b_cd64 and earlier allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.jenkins.plugins:opentelemetry | all versions | 3.1543.1545.vf5aio.jenkins.plugins:opentelemetry:3.1543.1545.vf5a |
Affected Products
opentelemetryjenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.jenkins.plugins:opentelemetry, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.jenkins.plugins:opentelemetry to 3.1543.1545.vf5a or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f696-867g-2759 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
Is GHSA-f696-867g-2759 in your dependencies?
Find it across Maven, including transitive dependencies.