Skip to main content
VulnerabilityPublished Updated

CVE-2022-41241: Jenkins RQM Plugin · XML External Entity (XXE)

Affects Jenkins RQM PluginSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 58% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Sep 2022

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Jenkins project Jenkins RQM PluginAffected
  • <=2.8
Fixed in–

AI-suggested

  1. Immediate upgrade or patching: Organizations should check for updates or patches from the Jenkins project or plugin maintainers that address CVE-2022-41241.
  2. XML parser hardening: If custom configurations are possible, ensure that the XML parser used by the plugin is configured to disable external entity processing and DTDs to prevent XXE attacks.
  3. Network segmentation: Restrict network access to Jenkins servers, limiting exposure to trusted internal networks and VPNs only. Avoid exposing Jenkins instances directly to the internet.
  4. Access controls: Enforce strict access controls and monitoring on Jenkins instances to detect anomalous activities that may indicate exploitation attempts.
  5. Monitoring and logging: Enable detailed logging of Jenkins plugin activities and monitor for suspicious XML payloads or unusual requests targeting the RQM Plugin endpoints.
  6. Incident response readiness: Prepare incident response plans specifically for Jenkins-related compromises, including credential rotation and forensic analysis procedures.
  7. Security awareness: Educate DevOps and development teams about the risks of XXE vulnerabilities and secure plugin management practices.

Description

Jenkins RQM Plugin 2.8 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.

References

Community reviews

Loading reviews…