{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:loadninja. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-33003 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:loadninja to 2.2 or later.","what":"CVE-2026-33003 is a medium-severity vulnerability in Jenkins LoadNinja Plugin, published on 18 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-33003 and fix it if it is affected.\n\nWhat it is: CVE-2026-33003 is a medium-severity vulnerability in Jenkins LoadNinja Plugin, published on 18 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-33003 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:loadninja (Maven): affected all versions; fixed in 2.2\n- org.jenkins-ci.plugins:loadninja (Maven): affected all versions; fixed in 2.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-33003/ (Markdown: https://insights.sbomify.com/CVE-2026-33003/index.md)","id":"CVE-2026-33003","markdown":"https://insights.sbomify.com/CVE-2026-33003/index.md","name":"CVE-2026-33003","record":{"aliases":["GHSA-qqjr-hf5h-jx3q"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins LoadNinja Plugin","requires_auth":"low_privilege","summary":"Attackers with extended read permissions or file system access can view unencrypted LoadNinja API keys stored in Jenkins job configurations.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"loadninja","vendor":"jenkins"}],"cvss":{"score":4.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Jenkins LoadNinja Plugin stores LoadNinja API keys unencrypted in job config.xml files","id":"CVE-2026-33003","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Jenkins LoadNinja Plugin does not mask LoadNinja API keys displayed on the job configuration form","id":"CVE-2026-33004"},"packages":[{"ecosystem":"Maven","fixed":["2.2"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:loadninja","purl":null,"source":"GHSA-qqjr-hf5h-jx3q"},{"ecosystem":"Maven","fixed":["2.2"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:loadninja","purl":"pkg:maven/org.jenkins-ci.plugins/loadninja","source":"GHSA-qqjr-hf5h-jx3q"}],"prev":{"headline":"Jenkins has a DNS rebinding vulnerability in WebSocket CLI origin validation","id":"CVE-2026-33002"},"products":["Jenkins LoadNinja Plugin"],"published":"2026-03-18","related":[{"cvss_score":4.3,"headline":"Jenkins LoadNinja Plugin does not mask LoadNinja API keys displayed on the job configuration form","id":"CVE-2026-33004","kev_date_added":null,"published":"2026-03-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-18","vendors":["Jenkins Project"]},"summary":"Attackers with extended read permissions or file system access can view unencrypted LoadNinja API keys stored in Jenkins job configurations.","url":"https://insights.sbomify.com/CVE-2026-33003/"}