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?

The records we use list no patched version of org.jenkins-ci.plugins.workflow:puppet-enterprise-pipeline for GHSA-mj9c-vjp9-pggh. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

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.

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 80th 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

Incorrect Authorization in Puppet Enterprise Pipeline Jenkins PluginGHSA-mj9c-vjp9-pggh

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. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asCVE-2019-10458

Published

May 24, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Nov 6, 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 CVEs80th percentile — riskier than 80% 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.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

Affected Products

1 product · 1 configurations

Application

puppet enterprise pipelinejenkins

≤ 1.3.1

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.workflow:puppet-enterprise-pipeline, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of org.jenkins-ci.plugins.workflow:puppet-enterprise-pipeline for GHSA-mj9c-vjp9-pggh. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
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.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

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

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works