CVE-2026-33003 json
Jenkins LoadNinja Plugin stores LoadNinja API keys unencrypted in job config.xml files
published 7mo ago modified 4mo ago also GHSA-qqjr-hf5h-jx3q , EUVD-2026-12847
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 4%
- public exploits
- 0
- none known
Summary
Jenkins LoadNinja Plugin 2.1 and earlier stores LoadNinja API keys unencrypted in job config.xml files on the Jenkins controller where they can be viewed by users with Item/Extended Read permission or access to the Jenkins controller file system.
Patch / fix
- maven org.jenkins-ci.plugins:loadninja 2.2
- jenkins loadninja 2.2
Is CVE-2026-33003 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 7mo ago
Exploit prediction
0.15% chance of exploitation in the next 30 days, higher than 4% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| GitHub | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jenkins-ci.plugins:loadninja | <2.2 |
2.2 |
Affected products
- Jenkins Project Jenkins LoadNinja Plugin
Classification
- Weakness
-
- CWE-312 Cleartext Storage of Sensitive Information
References
-
jenkins.io
/security/advisory/2026-03-18/#SECURITY-3642
vendor-advisory, web
-
nvd.nist.gov
/vuln/detail/CVE-2026-33003
advisory
-
github.com
/jenkinsci/loadninja-plugin
package
Sources
- CVE List CVE-2026-33003
- GitHub Advisory GHSA-qqjr-hf5h-jx3q
- NVD CVE-2026-33003
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.