How severe is CVE-2022-34179?

CVE-2022-34179 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-34179?

CVE-2022-34179 affects the following packages: org.jenkins-ci.plugins:embeddable-build-status (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-34179?

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

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

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

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

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

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

No public exploit code has been indexed for CVE-2022-34179 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-34179?

CVE-2022-34179 has an EPSS (Exploit Prediction Scoring System) score of 1.8%, placing it in the 78th 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-34179?

CVE-2022-34179 is classified as Path Traversal (CWE-22). 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-34179 published, and has it been updated?

CVE-2022-34179 was published on June 23, 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

HIGH severity

CVE-2022-34179 — embeddable-build-status

HIGHFix: jenkinsci/embeddable-build-status-plugin@63f82f2

CVE-2022-34179 is a high-severity (CVSS 7.5) Path Traversal vulnerability in org.jenkins-ci.plugins:embeddable-build-status. A fix is available for org.jenkins-ci.plugins:embeddable-build-status — see the affected versions and patch details below.

Path Traversal vulnerability in Jenkins Embeddable Build Status Plugin

Also known asGHSA-93mx-2vf9-28c4

Published

Jun 23, 2022

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.8%probability of exploitation in next 30 days

Lower Risk+0.06%

Lower risk than most CVEs78th percentile — riskier than 78% 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

1 pkg affected

☕org.jenkins-ci.plugins:embeddable-build-status

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 Embeddable Build Status Plugin 2.0.3 and earlier allows specifying a style query parameter that is used to choose a different SVG image style without restricting possible values, resulting in a relative path traversal vulnerability that allows attackers without Overall/Read permission to specify paths to other SVG images on the Jenkins controller file system.

Embeddable Build Status Plugin 2.0.4 restricts the style query parameter to one of the three legal values.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:embeddable-build-status`	all versions	2.0.4`org.jenkins-ci.plugins:embeddable-build-status:2.0.4`

Affected Products

1 product · 1 configurations

Application

embeddable build statusjenkins

≤ 2.0.3

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:embeddable-build-status, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:embeddable-build-status to 2.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-34179 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

Jenkins Embeddable Build Status Plugin 2.0.3 and earlier allows specifying a `style` query parameter that is used to choose a different SVG image style without restricting possible values, resulting in a relative path traversal vulnerability that allows attackers without Overall/Read permission to specify paths to other SVG images on the Jenkins controller file system. Embeddable Build Status Plugin 2.0.4 restricts the `style` query parameter to one of the three legal values.

O3 Security · Impact-Aware SCA

Is CVE-2022-34179 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

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

CWE Classification

CWE-22Path Traversal

Weaponization

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

Timeline

Disclosed

Jun 23, 2022

Last updated

Oct 24, 2026

Identifiers

CVE-2022-34179

GHSA-93mx-2vf9-28c4

References

Advisoryjenkins.io · 2022 06 22 Advisorynvd.nist.gov · CVE 2022 34179 Webgithub.com · 63f82f28d989d30a23089a0a66c11f222651a8c6 Packagegithub.com · embeddable build status plugin

Related vulnerabilities

Also affects embeddable-build-status

This CVE is high severity; 1 of 2 other CVEs affecting embeddable-build-status is rated as high or higher (top: high).

CVE-2022-34178CVE-2022-34180

Same weakness: CWE-22

This CVE is high severity; 3 of 6 other CVEs with CWE-22 are rated as high or higher (top: critical).

CVE-2026-62331GHSA-4xm8-rg9h-jhq2CVE-2026-9083CVE-2026-115908CVE-2026-118667CVE-2026-118654Browse all CWE-22

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2022-34179 — embeddable-build-status

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2022-34179 in your dependencies?