How severe is CVE-2022-29866?

No CVSS score has been assigned to CVE-2022-29866 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2022-29866?

CVE-2022-29866 affects the following packages: OPCFoundation.NetStandard.Opc.Ua.Core (NuGet). Ecosystems affected: NuGet.

How do I fix CVE-2022-29866?

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 CVE-2022-29866 is resolved across your whole dependency graph.

How do I detect CVE-2022-29866 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 CVE-2022-29866 if there is no patch (or I can't update yet)?

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 does O3 Security protect against CVE-2022-29866?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-29866 can be triaged on real exposure rather than presence alone.

Is CVE-2022-29866 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-29866 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 CVE-2022-29866?

CVE-2022-29866 has an EPSS (Exploit Prediction Scoring System) score of 1.7%, placing it in the 76th 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 CVE-2022-29866?

CVE-2022-29866 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 CVE-2022-29866 published, and has it been updated?

CVE-2022-29866 was published on June 16, 2022 and was last updated on August 12, 2026. 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

CVE-2022-29866 — OPCFoundation.NetStandard…

CVE-2022-29866 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.

Uncontrolled Resource Consumption in OPCFoundation.NetStandard.Opc.Ua.Core

Also known asGHSA-6fp8-cxc9-4fr9

Published

Jun 16, 2022

Updated

Aug 12, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs76th percentile — riskier than 76% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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`

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 CVE-2022-29866 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-29866 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2022-29866. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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 CVE-2022-29866 in your dependencies?

O3 Security finds CVE-2022-29866 across NuGet dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works