OpenCRX allows a remote attacker to execute arbitrary code via a crafted requestGHSA-q74f-rf27-8hxc
CRITICALFix: opencrx/opencrx@ce7a71dGHSA-q74f-rf27-8hxc is a critical-severity (CVSS 9.8) XML External Entity (XXE) vulnerability in org.opencrx:opencrx-client. A fix is available for org.opencrx:opencrx-client — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-q74f-rf27-8hxc.
EPSS Exploitation Probability
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
org.opencrx:opencrx-clientReal-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 issue in openCRX v.5.2.2 allows a remote attacker to read internal files and execute server side request forgery attack via insecure DocumentBuilderFactory.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.opencrx:opencrx-client | all versions | 5.3.0org.opencrx:opencrx-client:5.3.0 |
Affected Products
opencrxopencrxDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.opencrx:opencrx-client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.opencrx:opencrx-client to 5.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q74f-rf27-8hxc is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.
Frequently Asked Questions
Is GHSA-q74f-rf27-8hxc in your dependencies?
Find it across Maven, including transitive dependencies.