CVE-2022-41249: Jenkins SCM HttpClient Plugin · Cross-Site Request Forgery
Affects Jenkins SCM HttpClient PluginSource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Sep 2022
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Jenkins project Jenkins SCM HttpClient Plugin | Affected
| Fixed in– |
AI-suggested
To mitigate this vulnerability, European organizations should: 1) Immediately update the Jenkins SCM HttpClient Plugin to a version later than 1.5 where the vulnerability is patched. If an update is not immediately possible, consider disabling the plugin temporarily. 2) Implement strict CSRF protection measures within Jenkins, including enabling the built-in CSRF protection features and validating all HTTP requests. 3) Restrict network access to Jenkins servers to trusted IP ranges and enforce strong authentication and authorization controls to limit exposure. 4) Audit and rotate credentials stored in Jenkins, especially those that could be targeted by this vulnerability. 5) Monitor Jenkins logs and network traffic for unusual outbound connections to unknown HTTP servers, which may indicate exploitation attempts. 6) Educate users to avoid clicking on suspicious links or visiting untrusted websites while authenticated to Jenkins. 7) Employ web application firewalls (WAFs) or reverse proxies to detect and block CSRF attack patterns targeting Jenkins endpoints.
Description
A cross-site request forgery (CSRF) vulnerability in Jenkins SCM HttpClient Plugin 1.5 and earlier allows attackers to connect to an attacker-specified HTTP server using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.