How severe is GHSA-qjq3-wqj5-g37q?

GHSA-qjq3-wqj5-g37q has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-qjq3-wqj5-g37q?

GHSA-qjq3-wqj5-g37q affects the following packages: io.jenkins.plugins:pipeline-groovy-lib (Maven). Ecosystems affected: Maven.

How do I fix GHSA-qjq3-wqj5-g37q?

Update io.jenkins.plugins:pipeline-groovy-lib to 798.v5cc688825312 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qjq3-wqj5-g37q is resolved across your whole dependency graph.

How do I detect GHSA-qjq3-wqj5-g37q in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.jenkins.plugins:pipeline-groovy-lib. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-qjq3-wqj5-g37q 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-qjq3-wqj5-g37q?

O3 pinpoints whether GHSA-qjq3-wqj5-g37q is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-qjq3-wqj5-g37q actively exploited in the wild?

No public exploit code has been indexed for GHSA-qjq3-wqj5-g37q 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-qjq3-wqj5-g37q?

GHSA-qjq3-wqj5-g37q has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 22th 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 GHSA-qjq3-wqj5-g37q?

GHSA-qjq3-wqj5-g37q is classified as CWE-59 (CWE-59). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-qjq3-wqj5-g37q published, and has it been updated?

GHSA-qjq3-wqj5-g37q was published on May 27, 2026 and was last updated on July 1, 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

GHSA-qjq3-wqj5-g37q

HIGH

Jenkins Pipeline: Groovy Libraries Plugin does not prohibit symbolic links in shared libraries

Also known asCVE-2026-48921

Published

May 27, 2026

Updated

Jul 1, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk22th percentile0.00%

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.

Blast Radius

1 pkg affected

☕io.jenkins.plugins:pipeline-groovy-lib

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 Pipeline: Groovy Libraries Plugin 797.v90ea_a_9b_e45a_0 and earlier does not prohibit symbolic links in shared libraries.

This allows attackers able to control the content of a library used by a Pipeline job to read arbitrary files on the Jenkins controller filesystem.

Pipeline: Groovy Libraries Plugin 798.v5cc688825312 prohibits symbolic links in shared libraries.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.jenkins.plugins:pipeline-groovy-lib`	all versions	798.v5cc688825312

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.jenkins.plugins:pipeline-groovy-lib. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update io.jenkins.plugins:pipeline-groovy-lib to 798.v5cc688825312 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qjq3-wqj5-g37q is resolved across your whole dependency graph.
Workarounds
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 pinpoints whether GHSA-qjq3-wqj5-g37q is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

Frequently Asked Questions

Jenkins Pipeline: Groovy Libraries Plugin 797.v90ea_a_9b_e45a_0 and earlier does not prohibit symbolic links in shared libraries. This allows attackers able to control the content of a library used by a Pipeline job to read arbitrary files on the Jenkins controller filesystem. Pipeline: Groovy Libraries Plugin 798.v5cc688825312 prohibits symbolic links in shared libraries.

O3 Security · Impact-Aware SCA

Is GHSA-qjq3-wqj5-g37q in your dependencies?

O3 detects GHSA-qjq3-wqj5-g37q across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works