Description
Jenkins 2.579 and earlier, LTS 2.568.2 and earlier does not escape map keys when serializing objects as JSON and Python through its REST API, allowing attackers able to control map property names to inject arbitrary fields into JSON and Python API responses.
Published: 2026-09-02
Score: 4.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Jenkins releases 2.579 and earlier, including LTS 2.568.2 and earlier, do not escape map keys during object serialization to JSON. Attackers who can control map property names are able to inject arbitrary fields into the JSON and Python responses generated by the REST API. This flaw, classified as CWE-116, allows an attacker to modify the structure of API responses, potentially misleading clients or providing a vector for further exploitation such as information disclosure or privilege escalation.

Affected Systems

The affected product is Jenkins by the Jenkins Project, specifically all releases up to and including version 2.579 and LTS 2.568.2. Any instance of Jenkins running one of these versions with a reachable REST API is vulnerable.

Risk and Exploitability

The CVSS score of 4.3 indicates moderate severity. EPSS information is not available and the vulnerability is not listed in the CISA KEV catalog. The likely attack vector involves sending crafted JSON payloads through the REST API, requiring the ability to influence map keys, such as through authenticated API calls or user-supplied input to Jenkins plugins. While no public exploits are known, the flaw permits arbitrary field injection, warranting timely remediation.

Generated by OpenCVE AI on September 3, 2026 at 11:48 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Jenkins to version 2.580 or later, or LTS 2.568.3 or newer, to obtain the vendor‑provided fix that properly escapes map keys
  • If upgrading immediately is not possible, restrict REST API access to trusted administrators and block unauthenticated calls to prevent attackers from supplying malicious map keys
  • Implement input validation to sanitize or remove map keys supplied by users before serialization, ensuring that only trusted data structures are converted to JSON

Generated by OpenCVE AI on September 3, 2026 at 11:48 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 03 Sep 2026 12:15:00 +0000

Type Values Removed Values Added
Title Unescaped Map Keys in Jenkins REST API Allow Field Injection

Thu, 03 Sep 2026 11:30:00 +0000

Type Values Removed Values Added
First Time appeared Jenkins Project
Jenkins Project jenkins
Vendors & Products Jenkins Project
Jenkins Project jenkins

Wed, 02 Sep 2026 18:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-116
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Wed, 02 Sep 2026 10:45:00 +0000

Type Values Removed Values Added
Description Jenkins 2.579 and earlier, LTS 2.568.2 and earlier does not escape map keys when serializing objects as JSON and Python through its REST API, allowing attackers able to control map property names to inject arbitrary fields into JSON and Python API responses.
References

Subscriptions

Jenkins Project Jenkins
cve-icon MITRE

Status: PUBLISHED

Assigner: jenkins

Published:

Updated: 2026-09-02T17:19:10.287Z

Reserved: 2026-09-01T21:55:27.033Z

Link: CVE-2026-84655

cve-icon Vulnrichment

Updated: 2026-09-02T17:19:02.456Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-09-02T16:17:30.177

Modified: 2026-09-03T17:13:16.490

Link: CVE-2026-84655

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-03T12:00:04Z

Weaknesses
  • CWE-116

    Improper Encoding or Escaping of Output