GHSA-pq4w-qm9g-qx68 is a high-severity (CVSS 7.4) Insufficient Random Values vulnerability in org.eclipse.milo:sdk-client. O3 Security confirms whether GHSA-pq4w-qm9g-qx68 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Insufficient Nonce Validation in Eclipse Milo Client
Real-World Exposure
org.eclipse.milo:sdk-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
Impact
Credential replay affecting those connected to a server when all 3 of the following conditions are met:
SecurityPolicyisNone- using username/password or X509-based authentication
- the server has a defect causing it to send null/empty or zeroed nonces
Patches
The problem has been patched in version 0.3.6. A more relaxed treatment of validation as agreed upon by the OPC UA Security Working Group is implemented in version 0.3.7.
Workarounds
Do not use username/password or X509-based authentication with SecurityPolicy of None.
References
For more information
If you have any questions or comments about this advisory:
- Open an issue at https://github.com/eclipse/milo/issues
- Email the mailing list
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.eclipse.milo:sdk-client | all versions | 0.3.6 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.milo:sdk-client. 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.eclipse.milo:sdk-client to 0.3.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pq4w-qm9g-qx68 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-pq4w-qm9g-qx68 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-pq4w-qm9g-qx68. 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-pq4w-qm9g-qx68 in your dependencies?
O3 detects GHSA-pq4w-qm9g-qx68 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.