Is OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4 vulnerable?
NuGet · 29 releases from 1.4.364.40 to 1.4.372.107 · latest OPCFoundation.NetStandard.Opc.Ua.Bindings.Https is 2.0.2 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4.372.107, the last 1.4 release, is affected by 1 known security advisory (1 medium), including CVE-2024-42513. Upgrade to 1.5.374.158 or later to fix all of them.
dotnet add package OPCFoundation.NetStandard.Opc.Ua.Bindings.Https --version 1.5.374.158Is your project on an affected OPCFoundation.NetStandard.Opc.Ua.Bindings.Https?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4.372.107
Security Update for the OPC UA .NET Standard Stack
- Affected
- <1.5.374.158
- Fixed in
- 1.5.374.158
Every OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4.x release
Affected: 1.4.364.40 to 1.4.372.107. Latest OPCFoundation.NetStandard.Opc.Ua.Bindings.Https: 2.0.2.
| Version | Known advisories |
|---|---|
| OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4.372.107 | CVE-2024-42513 |
| OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4.372.106 | CVE-2024-42513 |
| OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4.372.76 | CVE-2024-42513 |
| OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4.372.56 | CVE-2024-42513 |
| OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4.371.96 | CVE-2024-42513 |
| OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4.371.91 | CVE-2024-42513 |
| OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4.371.86 | CVE-2024-42513 |
| OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4.371.60 | CVE-2024-42513 |
| OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4.371.50 | CVE-2024-42513 |
| OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4.371.41 | CVE-2024-42513 |
| OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4.370.12 | CVE-2024-42513 |
| OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4.370.9 | CVE-2024-42513 |
| OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4.370.1 | CVE-2024-42513 |
| OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4.369.30 | CVE-2024-42513 |
| OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4.368.58 | CVE-2024-42513 |
| OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4.368.53 | CVE-2024-42513 |
| OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4.368.33 | CVE-2024-42513 |
| OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4.367.100 | CVE-2024-42513 |
| OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4.367.95 | CVE-2024-42513 |
| OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4.367.75 | CVE-2024-42513 |
| OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4.367.42 | CVE-2024-42513 |
| OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4.367.41 | CVE-2024-42513 |
| OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4.367.39 | CVE-2024-42513 |
| OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4.366.38 | CVE-2024-42513 |
| OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4.365.48 | CVE-2024-42513 |
| OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4.365.23 | CVE-2024-42513 |
| OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4.365.10 | CVE-2024-42513 |
| OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4.365.2 | CVE-2024-42513 |
| OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4.364.40 | CVE-2024-42513 |
Which of your client projects are still on OPCFoundation.NetStandard.Opc.Ua.Bindings.Https 1.4?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact OPCFoundation.NetStandard.Opc.Ua.Bindings.Https version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other OPCFoundation.NetStandard.Opc.Ua.Bindings.Https versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the NuGet registry. Refreshed daily.