How severe is CVE-2022-29049?

CVE-2022-29049 has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-29049?

CVE-2022-29049 affects the following packages: org.jenkins-ci.plugins:promoted-builds (Maven), org.jenkins-ci.plugins:promoted-builds (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-29049?

Update org.jenkins-ci.plugins:promoted-builds to 3.10.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-29049 is resolved across your whole dependency graph.

How do I detect CVE-2022-29049 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:promoted-builds, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-29049 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2022-29049 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-29049 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-29049?

CVE-2022-29049 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 57th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-29049?

CVE-2022-29049 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2022-29049 published, and has it been updated?

CVE-2022-29049 was published on April 12, 2022 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2022-29049 — promoted-builds

MEDIUMFix: jenkinsci/promoted-builds-plugin@d6fd956

CVE-2022-29049 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in org.jenkins-ci.plugins:promoted-builds. A fix is available for org.jenkins-ci.plugins:promoted-builds — see the affected versions and patch details below.

Promotion names in Jenkins promoted builds Plugin are not validated when using Job DSL

Also known asGHSA-jmxr-w2jc-qp7w

Published

Apr 12, 2022

Updated

Oct 24, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs57th percentile — riskier than 57% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

☕org.jenkins-ci.plugins:promoted-builds☕org.jenkins-ci.plugins:promoted-builds

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Jenkins promoted builds Plugin provides dedicated support for defining promotions using Job DSL Plugin.

promoted builds Plugin 873.v6149db_d64130 and earlier does not validate the names of promotions defined in Job DSL. This allows attackers with Job/Configure permission to create a promotion with an unsafe name. As a result, the promotion name could be used for cross-site scripting (XSS) or to replace other config.xml files.

promoted builds Plugin 876.v99d29788b_36b_ and 3.10.1 validates the name of promotions.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:promoted-builds`	all versions	3.10.1`org.jenkins-ci.plugins:promoted-builds:3.10.1`
☕Maven	`org.jenkins-ci.plugins:promoted-builds`	≥ 3.11&&< 876.v99d29788b	876.v99d29788b`org.jenkins-ci.plugins:promoted-builds:876.v99d29788b`

Affected Products

1 product · 2 configurations

Application

promoted buildsjenkins

≥ 867.v7c3a_b_83a_eb_79 && < 876.v99d29788b_36b_

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:promoted-builds, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:promoted-builds to 3.10.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-29049 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

Jenkins promoted builds Plugin provides dedicated support for defining promotions using [Job DSL Plugin](https://plugins.jenkins.io/job-dsl). promoted builds Plugin 873.v6149db_d64130 and earlier does not validate the names of promotions defined in Job DSL. This allows attackers with Job/Configure permission to create a promotion with an unsafe name. As a result, the promotion name could be used for cross-site scripting (XSS) or to replace other `config.xml` files. promoted builds Plugin 876.v99d29788b_36b_ and 3.10.1 validates the name of promotions.

O3 Security · Impact-Aware SCA

Is CVE-2022-29049 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.4/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

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

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Apr 12, 2022

Last updated

Oct 24, 2026

Identifiers

CVE-2022-29049

GHSA-jmxr-w2jc-qp7w

References

Advisoryjenkins.io · 2022 04 12 Advisorynvd.nist.gov · CVE 2022 29049 Webgithub.com · d6fd95688ae2052bf9ac7158bc2579c755167fe0 Packagegithub.com · promoted builds plugin

Related vulnerabilities

Also affects promoted-builds

This CVE is medium severity; 3 of 3 other CVEs affecting promoted-builds are rated as high or higher (top: high).

CVE-2021-21641CVE-2018-1000114CVE-2022-29045

Same weakness: CWE-79

This CVE is medium severity; 3 of 5 other CVEs with CWE-79 are rated as high or higher (top: high).

CVE-2026-126075CVE-2026-126063CVE-2026-110802CVE-2026-123364CVE-2026-118670Browse all CWE-79

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026