How severe is GHSA-2gh6-wc3m-g37f?

GHSA-2gh6-wc3m-g37f has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-2gh6-wc3m-g37f?

GHSA-2gh6-wc3m-g37f affects the following packages: pl.allegro.tech.hermes:hermes-management (Maven). Ecosystems affected: Maven.

How do I fix GHSA-2gh6-wc3m-g37f?

Update pl.allegro.tech.hermes:hermes-management to 2.2.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2gh6-wc3m-g37f is resolved across your whole dependency graph.

How do I detect GHSA-2gh6-wc3m-g37f in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pl.allegro.tech.hermes:hermes-management, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-2gh6-wc3m-g37f 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-2gh6-wc3m-g37f?

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

Is GHSA-2gh6-wc3m-g37f actively exploited in the wild?

No public exploit code has been indexed for GHSA-2gh6-wc3m-g37f 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.

When was GHSA-2gh6-wc3m-g37f published, and has it been updated?

GHSA-2gh6-wc3m-g37f was published on September 17, 2024 and was last updated on August 31, 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

CRITICAL severity

GHSA-2gh6-wc3m-g37f — hermes-management

CRITICALFix: allegro/hermes@72ecc5a

GHSA-2gh6-wc3m-g37f is a critical-severity (CVSS 9.8) remote code execution vulnerability in pl.allegro.tech.hermes:hermes-management. A fix is available for pl.allegro.tech.hermes:hermes-management — see the affected versions and patch details below.

hermes-management is vulnerable to RCE due to Apache commons-jxpath

Published

Sep 17, 2024

Updated

Aug 31, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 31, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

☕pl.allegro.tech.hermes:hermes-management

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

Impact

hermes-management is vulnerable to RCE when it processes user-controlled data due to using Apache commons-jxpath.

Patches

Upgrade Hermes to at least hermes-2.2.9

References

https://hackinglab.cz/en/blog/remote-code-execution-in-jxpath-library-cve-2022-41852/

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`pl.allegro.tech.hermes:hermes-management`	≥ 0.8.2&&< 2.2.9	2.2.9`pl.allegro.tech.hermes:hermes-management:2.2.9`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pl.allegro.tech.hermes:hermes-management, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pl.allegro.tech.hermes:hermes-management to 2.2.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2gh6-wc3m-g37f 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2gh6-wc3m-g37f can be triaged on real exposure rather than presence alone.

Tailored to GHSA-2gh6-wc3m-g37f. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact hermes-management is vulnerable to RCE when it processes user-controlled data due to using Apache commons-jxpath. ### Patches Upgrade Hermes to at least hermes-2.2.9 ### References https://hackinglab.cz/en/blog/remote-code-execution-in-jxpath-library-cve-2022-41852/

O3 Security · Impact-Aware SCA

Is GHSA-2gh6-wc3m-g37f in your dependencies?

O3 Security finds GHSA-2gh6-wc3m-g37f 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