CVE-2022-25304: PYSEC-2026-888 - Uncontrolled Resource Consumption in asyncua and opcua

CVE-2022-25304 · Severity: low · CVSS 3.1 · Published 2026-07-06

Uncontrolled Resource Consumption in asyncua and opcua

Technologies: asyncua (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2022-25304 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2022-25304 being exploited in the wild.
How severe is CVE-2022-25304?
Low severity, with a CVSS score of 3.1, published 6 July 2026.
Which products and versions are affected?
asyncua (PyPI) ECOSYSTEM:introduced=0,fixed=0.9.96; opcua (PyPI) ECOSYSTEM:introduced=0,last_affected=0.98.13.
Is there a fix for CVE-2022-25304?
Yes. asyncua (PyPI): upgrade to 0.9.96 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2022-25304?
Check whether you run asyncua (PyPI) or opcua (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • asyncua (PyPI): upgrade to 0.9.96 or later
    pip install "asyncua>=0.9.96"

Affected products

  • asyncua (PyPI) ECOSYSTEM:introduced=0,fixed=0.9.96
  • opcua (PyPI) ECOSYSTEM:introduced=0,last_affected=0.98.13

Identifiers

  • CVE-2022-25304
  • GHSA-mfpj-3qhm-976m
  • PYSEC-2026-2385
  • PYSEC-2026-888

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.