How severe is GHSA-6fp8-cxc9-4fr9?

No CVSS score has been assigned to GHSA-6fp8-cxc9-4fr9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6fp8-cxc9-4fr9?

GHSA-6fp8-cxc9-4fr9 affects the following packages: OPCFoundation.NetStandard.Opc.Ua.Core (NuGet). Ecosystems affected: NuGet.

How do I fix GHSA-6fp8-cxc9-4fr9?

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-6fp8-cxc9-4fr9 is resolved across your whole dependency graph.

How do I detect GHSA-6fp8-cxc9-4fr9 in my NuGet dependencies?

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.

How do I mitigate GHSA-6fp8-cxc9-4fr9 if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is GHSA-6fp8-cxc9-4fr9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-6fp8-cxc9-4fr9 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-6fp8-cxc9-4fr9?

GHSA-6fp8-cxc9-4fr9 has an EPSS (Exploit Prediction Scoring System) score of 1.7%, placing it in the 77th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-6fp8-cxc9-4fr9?

GHSA-6fp8-cxc9-4fr9 is classified as Uncontrolled Resource Consumption (CWE-400). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-6fp8-cxc9-4fr9 published, and has it been updated?

GHSA-6fp8-cxc9-4fr9 was published on June 17, 2022 and was last updated on December 1, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET NuGet

Not in CISA KEV

Uncontrolled Resource Consumption in OPCFoundation.NetStandard.Opc.Ua.CoreGHSA-6fp8-cxc9-4fr9

GHSA-6fp8-cxc9-4fr9 is a Uncontrolled Resource Consumption 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-29866

Published

Jun 17, 2022

Updated

Dec 1, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.7%probability of exploitation in next 30 days

Lower Risk+0.03%

Lower risk than most CVEs77th percentile — riskier than 77% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

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 to trigger a stack overflow exception in a server that exposes an HTTPS endpoint.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`OPCFoundation.NetStandard.Opc.Ua.Core`	all versions	1.4.368.58`dotnet 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

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.
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-6fp8-cxc9-4fr9 is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

A vulnerability was discovered in the OPC UA .NET Standard Stack that allows a malicious client to trigger a stack overflow exception in a server that exposes an HTTPS endpoint.

O3 Security · Impact-Aware SCA

Is GHSA-6fp8-cxc9-4fr9 in your dependencies?

Find it across NuGet, including transitive dependencies.

Scan my dependencies How O3 SCA works