How severe is GHSA-mj9c-vjp9-pggh?

GHSA-mj9c-vjp9-pggh has a CVSS score of 9.9/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-mj9c-vjp9-pggh?

GHSA-mj9c-vjp9-pggh affects the following packages: org.jenkins-ci.plugins.workflow:puppet-enterprise-pipeline (Maven). Ecosystems affected: Maven.

How do I fix GHSA-mj9c-vjp9-pggh?

No patched version of org.jenkins-ci.plugins.workflow:puppet-enterprise-pipeline has shipped for GHSA-mj9c-vjp9-pggh yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-mj9c-vjp9-pggh in my Maven dependencies?

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

How do I mitigate GHSA-mj9c-vjp9-pggh if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-mj9c-vjp9-pggh?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-mj9c-vjp9-pggh can be triaged on real exposure rather than presence alone.

Is GHSA-mj9c-vjp9-pggh actively exploited in the wild?

No public exploit code has been indexed for GHSA-mj9c-vjp9-pggh 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 GHSA-mj9c-vjp9-pggh?

GHSA-mj9c-vjp9-pggh has an EPSS (Exploit Prediction Scoring System) score of 1.9%, placing it in the 79th 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.

When was GHSA-mj9c-vjp9-pggh published, and has it been updated?

GHSA-mj9c-vjp9-pggh was published on May 24, 2022 and was last updated on November 8, 2023. 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

CRITICAL severity

GHSA-mj9c-vjp9-pggh — puppet-enterprise-pipeline

CRITICAL

GHSA-mj9c-vjp9-pggh is a critical-severity (CVSS 9.9) remote code execution vulnerability in org.jenkins-ci.plugins.workflow:puppet-enterprise-pipeline. No vendor fix is recorded yet; mitigation options are listed below.

Incorrect Authorization in Puppet Enterprise Pipeline Jenkins Plugin

Also known asCVE-2019-10458

Published

May 24, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

None yet

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs79th percentile — riskier than 79% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-mj9c-vjp9-pggh plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

1 pkg affected

☕org.jenkins-ci.plugins.workflow:puppet-enterprise-pipeline

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 Puppet Enterprise Pipeline 1.3.1 and earlier specifies unsafe values in its custom Script Security whitelist, allowing attackers able to execute Script Security protected scripts to execute arbitrary code.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins.workflow:puppet-enterprise-pipeline`	all versions	No fix

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.workflow:puppet-enterprise-pipeline, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of org.jenkins-ci.plugins.workflow:puppet-enterprise-pipeline has shipped for GHSA-mj9c-vjp9-pggh yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-mj9c-vjp9-pggh can be triaged on real exposure rather than presence alone.

Tailored to GHSA-mj9c-vjp9-pggh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-mj9c-vjp9-pggh in your dependencies?

O3 Security finds GHSA-mj9c-vjp9-pggh across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works