GHSA-pv39-qp28-4mgh is a critical-severity (CVSS 9.8) XML External Entity (XXE) vulnerability in com.predic8:soa-model-parent. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-pv39-qp28-4mgh is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Improper Restriction of XML External Entity Reference in soa-model
Real-World Exposure
com.predic8:soa-model-parent☕com.predic8:soa-model-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
Soa-model is a toolkit and Java API for WSDL, WADL and XML Schema. An XML External Entity (XXE) vulnerability exists in versions of soa-model prior to 1.6.4 in the WSDLParser function. This issue has been fixed in version 1.6.4.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.predic8:soa-model-parent | all versions | 1.6.4 |
| ☕Maven | com.predic8:soa-model-core | all versions | 1.6.4 |
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 com.predic8:soa-model-parent. 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 com.predic8:soa-model-parent to 1.6.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pv39-qp28-4mgh 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-pv39-qp28-4mgh 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-pv39-qp28-4mgh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-pv39-qp28-4mgh in your dependencies?
O3 detects GHSA-pv39-qp28-4mgh across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.