VulnerabilityPublished 18 Mar 2026

CVE-2026-33004: Jenkins LoadNinja Plugin · Information Exposure

Affects Jenkins LoadNinja PluginSource CVE Database V5

Compare

Not known to be exploited · CVSS 4.3 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Jenkins ProjectJenkins LoadNinja Plugin	Affected <=2.1	Fixed in–

AI-suggested

To mitigate this vulnerability, organizations should immediately audit and restrict access permissions to Jenkins job configurations, ensuring only trusted users have the ability to view or edit jobs using the LoadNinja Plugin. Implement role-based access control (RBAC) to minimize exposure. Until an official patch is released, consider removing or disabling the LoadNinja Plugin if it is not essential. If the plugin is required, avoid storing API keys directly in job configurations or use environment variables or Jenkins credentials store with proper masking. Regularly rotate LoadNinja API keys to limit the window of exposure in case of leakage. Monitor Jenkins logs and LoadNinja usage for any unusual activity that could indicate misuse of exposed keys. Stay updated with Jenkins security advisories for any forthcoming patches addressing this issue.

Description

CVE-2026-33004 is a medium-severity vulnerability in Jenkins LoadNinja Plugin version 2.1 and earlier where LoadNinja API keys are not masked in the job configuration form. This exposure allows attackers with at least low-level privileges to view sensitive API keys, potentially leading to unauthorized access to LoadNinja services. The vulnerability does not require user interaction and can be exploited remotely over the network. While it does not impact integrity or availability directly, the confidentiality breach can facilitate further attacks. No known exploits are currently reported in the wild. Organizations using Jenkins with the LoadNinja Plugin should review access controls and monitor for suspicious activity involving API keys. Patching or mitigating this issue is critical to prevent credential leakage.

Impact

The primary impact of this vulnerability is the potential exposure of LoadNinja API keys to unauthorized users who have access to Jenkins job configurations. This can lead to unauthorized access to LoadNinja services, allowing attackers to execute actions or retrieve data that the API keys permit. While the vulnerability does not directly compromise the Jenkins server's integrity or availability, the leaked credentials can be leveraged for further attacks, including data exfiltration, manipulation of load testing configurations, or abuse of LoadNinja resources. Organizations relying on Jenkins for continuous integration and using the LoadNinja Plugin are at risk, especially if access controls are lax or if multiple users have configuration access. The risk is heightened in environments where Jenkins is exposed to a broader user base or where API keys have broad privileges. Although no active exploitation is reported, the ease of viewing keys once access is obtained makes this a significant confidentiality concern.

Summary

The vulnerability identified as CVE-2026-33004 affects Jenkins LoadNinja Plugin versions 2.1 and earlier. The core issue is that the plugin fails to mask LoadNinja API keys when displayed in the Jenkins job configuration form. This means that any user with permission to view or edit job configurations can see the API keys in plaintext. Since these keys grant access to LoadNinja services, their exposure increases the risk of unauthorized use or abuse of LoadNinja resources. The vulnerability is classified under CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor). The CVSS v3.1 base score is 4.3, reflecting a medium severity level, with an attack vector of network (remote), low attack complexity, requiring low privileges, no user interaction, and impacting confidentiality only. The vulnerability does not affect integrity or availability. No patches or fixes are currently linked, and no known exploits have been reported in the wild. The issue arises from insufficient masking or obfuscation of sensitive data in the plugin's UI, a common security oversight in credential management within CI/CD tools.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

jenkins.io/security/advisory/2026-03-18/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Mar 2026, 01:15 UTC

WeaknessesCWE-200

Technical details

References

Community reviews

Related threats