GHSA-hfpg-gqjw-779m is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in org.jolokia:jolokia-core. 2 public exploit references exist, so weaponization risk is real. A fix is available for org.jolokia:jolokia-core — see the affected versions and patch details below.
Cross-site Scripting in Jolokia agent
EPSS Exploitation Probability
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-hfpg-gqjw-779m 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–50% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.jolokia:jolokia-coreReal-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
An XSS vulnerability exists in the Jolokia agent version 1.3.7 in the HTTP servlet that allows an attacker to execute malicious javascript in the victim's browser.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jolokia:jolokia-core | ≥ 1.3.7&&< 1.5.0 | 1.5.0org.jolokia:jolokia-core:1.5.0 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jolokia:jolokia-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jolokia:jolokia-core to 1.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hfpg-gqjw-779m 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-hfpg-gqjw-779m can be triaged on real exposure rather than presence alone.
Tailored to GHSA-hfpg-gqjw-779m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
How to detect GHSA-hfpg-gqjw-779m
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id ghsa-hfpg-gqjw-779m -u https://target- Template
- Jolokia 1.3.7 - Cross-Site Scripting
- Severity
- medium
- Impact
- Successful exploitation of this vulnerability could allow an attacker to execute arbitrary JavaScript code in the victim's browser, leading to session hijacking, defacement, or theft of sensitive information.
- Remediation
- Upgrade to a patched version of Jolokia or apply the necessary security patches to mitigate the XSS vulnerability.
Template by ProjectDiscovery nuclei-templates (mavericknerd, 0h1in9e, daffainfo), MIT licensed. View the full template. Scan only systems you are authorised to test.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Red Hat Product Security has rated this issue as having security impact of Low for: * Red Hat OpenStack Platform 9.0 (Mitaka) * Red Hat OpenStack Platform 10.0 (Newton) * Red Hat OpenStack Platform 11.0 (Ocata) * Red Hat OpenStack Platform 12.0 (Pike) Although the affected code is present in shipped packages, data…
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat JBoss A-MQ 6.3 | jolokia-core | RHSA-2018:3817 |
| Red Hat JBoss Fuse 7 | jolokia-core | RHSA-2018:2669 |
Frequently Asked Questions
Is GHSA-hfpg-gqjw-779m in your dependencies?
O3 Security finds GHSA-hfpg-gqjw-779m across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.