Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-70430

Jenkins: Jenkins: Privilege escalation via unrestricted object instantiation in project naming strategy configuration

Overview

Published
5 Aug 2026
Modified
24 Oct 2026
Low CVE
1 Registry packages
2 OS packages
3 Linux distributions
Yes Fix available

Description

Jenkins 2.575 and earlier, LTS 2.568.1 and earlier does not restrict the types of objects that can be instantiated as part of the project naming strategy configuration, allowing attackers with Overall/Manage permission to instantiate arbitrary types related to configuration, including those intended for configuration only by administrators.

Source: OX vulnerability database

Severity

2.7 · LOW

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

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

Weakness: CWE-284

Affected packages · 1

Packages affected by CVE-2026-70430
EcosystemPackageVulnerableFixed in
Bitnami jenkins <2.568.2>=2.569.0, <2.576.0 2.568.22.576.0

Open a package to see all its vulnerabilities.

Operating systems · 4 fixes

alpine 1 release · 1 package

fixed 1
jenkins
alpine fixes for CVE-2026-70430
ReleasePackageFixed in
edge jenkins 2.580.2-r0

chainguard 1 release · 1 package

fixed 1
jenkins-2-568
chainguard fixes for CVE-2026-70430
ReleasePackageFixed in
jenkins-2-568 2.568.2-r0

minimos 1 release · 2 packages

fixed 2
jenkins-2-568 jenkins
minimos fixes for CVE-2026-70430
ReleasePackageFixed in
jenkins-2-568 2.568.2-r0
jenkins 2.576-r0

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.