Insufficient Nonce Validation in Eclipse Milo Client

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.4 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS

• CVE-2019-19135: 1.04% estimated exploitation activity in the next 30 days; percentile 64.15 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Credential replay affecting those connected to a server when all 3 of the following conditions are met: - SecurityPolicy is None - 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 https://opcfoundation.org/SecurityBulletins/OPC%20Foundation%20Security%20Bulletin%20CVE-2019-19135.pdf 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

Published by the source

16 Mar 2020, 22:46 UTC

Last modified by the source

1 Feb 2023, 05:03 UTC

Source last checked

26 Oct 2026, 16:05 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-pq4w-qm9g-qx68

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2019-19135

Advisory: Insufficient Nonce Validation in Eclipse Milo Client
IDs: CVE-2019-19135, GHSA-pq4w-qm9g-qx68
Record: https://patchnext.com/advisories/cve-2019-19135 (revision 1, source checked 26 Oct 2026, 16:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.eclipse.milo:sdk-client 0.3.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.eclipse.milo:sdk-client: affected <= 0.3.4; fixed in 0.3.6

## Suggested inspection (read-only)
- Maven org.eclipse.milo:sdk-client: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.eclipse.milo:sdk-client.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-pq4w-qm9g-qx68 (GitHub-reviewed advisory GHSA-pq4w-qm9g-qx68 lists affected ranges: Maven org.eclipse.milo:sdk-client >=0 <=0.3.4)

Commands are suggestions: review each one before running it.