NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
.NET
.NET NuGet
Not in CISA KEV
HIGH severity

Incorrect Implementation of Authentication Algorithm in OPCFoundation.NetStandard.Opc.Ua.CoreGHSA-fvxf-r9fw-49pc

HIGH

GHSA-fvxf-r9fw-49pc is a high-severity (CVSS 7.5) Improper Authentication vulnerability in OPCFoundation.NetStandard.Opc.Ua.Core. A fix is available for OPCFoundation.NetStandard.Opc.Ua.Core — see the affected versions and patch details below.

Also known asCVE-2022-29865
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs76th percentile — riskier than 76% of all scored CVEsHighest risk
0.17%0.83%1.50%2.17%0.7%1.6%May 26Sep 26Nov 26

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

1 pkg affected
.NETOPCFoundation.NetStandard.Opc.Ua.Core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

A vulnerability was discovered in the OPC UA .NET Standard Stack that

  • allows a malicious client or server to bypass the application authentication mechanism
  • and allow a connection to an untrusted peer.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetOPCFoundation.NetStandard.Opc.Ua.Coreall versions1.4.368.58dotnet add package OPCFoundation.NetStandard.Opc.Ua.Core --version 1.4.368.58

Affected Products

1 product · 1 configurations
Application
ua .net standard stackopcfoundation
< 1.4.368.58
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for OPCFoundation.NetStandard.Opc.Ua.Core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update OPCFoundation.NetStandard.Opc.Ua.Core to 1.4.368.58 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fvxf-r9fw-49pc is resolved across your whole dependency graph.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

A vulnerability was discovered in the OPC UA .NET Standard Stack that - allows a malicious client or server to bypass the application authentication mechanism - and allow a connection to an untrusted peer.
O3 Security · Impact-Aware SCA

Is GHSA-fvxf-r9fw-49pc in your dependencies?

Find it across NuGet, including transitive dependencies.

Scan my dependencies How O3 SCA works
Incorrect Implementation of Authentication Algorithm in…