How severe is GHSA-jg2g-4rjg-cmqh?

GHSA-jg2g-4rjg-cmqh has a CVSS score of 9.9/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-jg2g-4rjg-cmqh?

GHSA-jg2g-4rjg-cmqh affects the following packages: org.apache.pulsar:pulsar-functions-worker (Maven), org.apache.pulsar:pulsar-functions-worker (Maven), org.apache.pulsar:pulsar-functions-worker (Maven), org.apache.pulsar:pulsar-functions-worker (Maven), org.apache.pulsar:pulsar-functions-worker (Maven). Ecosystems affected: Maven.

How do I fix GHSA-jg2g-4rjg-cmqh?

Update org.apache.pulsar:pulsar-functions-worker to 2.10.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jg2g-4rjg-cmqh is resolved across your whole dependency graph.

How do I detect GHSA-jg2g-4rjg-cmqh in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.pulsar:pulsar-functions-worker. 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-jg2g-4rjg-cmqh 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-jg2g-4rjg-cmqh?

O3 pinpoints whether GHSA-jg2g-4rjg-cmqh 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-jg2g-4rjg-cmqh actively exploited in the wild?

No public exploit code has been indexed for GHSA-jg2g-4rjg-cmqh 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-jg2g-4rjg-cmqh?

GHSA-jg2g-4rjg-cmqh has an EPSS (Exploit Prediction Scoring System) score of 56.9%, placing it in the 99th 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. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

When was GHSA-jg2g-4rjg-cmqh published, and has it been updated?

GHSA-jg2g-4rjg-cmqh was published on March 12, 2024 and was last updated on January 21, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-jg2g-4rjg-cmqh: pulsar-functions-worker Path Traversal (Cr…

EPSS Exploitation Probability

via FIRST.org ↗

56.9%probability of exploitation in next 30 days

High Risk99th percentile+55.90%

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

5 pkgs affected

☕org.apache.pulsar:pulsar-functions-worker☕org.apache.pulsar:pulsar-functions-worker☕org.apache.pulsar:pulsar-functions-worker☕org.apache.pulsar:pulsar-functions-worker☕org.apache.pulsar:pulsar-functions-worker

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

In Pulsar Functions Worker, authenticated users can upload functions in jar or nar files. These files, essentially zip files, are extracted by the Functions Worker. However, if a malicious file is uploaded, it could exploit a directory traversal vulnerability. This occurs when the filenames in the zip files, which aren't properly validated, contain special elements like "..", altering the directory path. This could allow an attacker to create or modify files outside of the designated extraction directory, potentially influencing system behavior. This vulnerability also applies to the Pulsar Broker when it is configured with "functionsWorkerEnabled=true".

This issue affects Apache Pulsar versions from 2.4.0 to 2.10.5, from 2.11.0 to 2.11.3, from 3.0.0 to 3.0.2, from 3.1.0 to 3.1.2, and 3.2.0.

2.10 Pulsar Function Worker users should upgrade to at least 2.10.6. 2.11 Pulsar Function Worker users should upgrade to at least 2.11.4. 3.0 Pulsar Function Worker users should upgrade to at least 3.0.3. 3.1 Pulsar Function Worker users should upgrade to at least 3.1.3. 3.2 Pulsar Function Worker users should upgrade to at least 3.2.1.

Users operating versions prior to those listed above should upgrade to the aforementioned patched versions or newer versions.

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.pulsar:pulsar-functions-worker`	≥ 2.4.0&&< 2.10.6	2.10.6
☕Maven	`org.apache.pulsar:pulsar-functions-worker`	≥ 2.11.0&&< 2.11.4	2.11.4
☕Maven	`org.apache.pulsar:pulsar-functions-worker`	≥ 3.0.0&&< 3.0.3	3.0.3
☕Maven	`org.apache.pulsar:pulsar-functions-worker`	≥ 3.1.0&&< 3.1.3	3.1.3
☕Maven	`org.apache.pulsar:pulsar-functions-worker`	≥ 3.2.0&&< 3.2.1	3.2.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.pulsar:pulsar-functions-worker. 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 org.apache.pulsar:pulsar-functions-worker to 2.10.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jg2g-4rjg-cmqh 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-jg2g-4rjg-cmqh 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-jg2g-4rjg-cmqh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In Pulsar Functions Worker, authenticated users can upload functions in jar or nar files. These files, essentially zip files, are extracted by the Functions Worker. However, if a malicious file is uploaded, it could exploit a directory traversal vulnerability. This occurs when the filenames in the zip files, which aren't properly validated, contain special elements like "..", altering the directory path. This could allow an attacker to create or modify files outside of the designated extraction directory, potentially influencing system behavior. This vulnerability also applies to the Pulsar Br

O3 Security · Impact-Aware SCA

Is GHSA-jg2g-4rjg-cmqh in your dependencies?

O3 detects GHSA-jg2g-4rjg-cmqh 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

GHSA-jg2g-4rjg-cmqh