CVE-2026-70430: Jenkins · Improper Access Control
Affects JenkinsSource CVE Database V5
Not known to be exploited · CVSS 2.7 Low.
Data as of 3 Nov 2026, 22:58 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 5 Aug 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 3 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Jenkins ProjectJenkins | Affected– | Fixed in– |
AI-suggested
Until a fix is available, restrict Overall/Manage permissions to trusted users only to reduce risk.
Description
A vulnerability in Jenkins versions 2.575 and earlier, including LTS 2.568.1 and earlier, allows attackers with Overall/Manage permission to instantiate arbitrary object types in the project naming strategy configuration. This can lead to unauthorized configuration changes intended only for administrators. The vulnerability has a low severity score and does not impact confidentiality or availability.