How severe is GHSA-m9vm-8mv9-v5v3?

No CVSS score has been assigned to GHSA-m9vm-8mv9-v5v3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-m9vm-8mv9-v5v3?

GHSA-m9vm-8mv9-v5v3 affects the following packages: ryu (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-m9vm-8mv9-v5v3?

No patched version of ryu has shipped for GHSA-m9vm-8mv9-v5v3 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-m9vm-8mv9-v5v3 in my PyPI dependencies?

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

How do I mitigate GHSA-m9vm-8mv9-v5v3 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 GHSA-m9vm-8mv9-v5v3?

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

Is GHSA-m9vm-8mv9-v5v3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-m9vm-8mv9-v5v3 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-m9vm-8mv9-v5v3?

GHSA-m9vm-8mv9-v5v3 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 51th 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-m9vm-8mv9-v5v3?

GHSA-m9vm-8mv9-v5v3 is classified as CWE-835 (CWE-835). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-m9vm-8mv9-v5v3 published, and has it been updated?

GHSA-m9vm-8mv9-v5v3 was published on May 5, 2024 and was last updated on July 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

GHSA-m9vm-8mv9-v5v3 — ryu

GHSA-m9vm-8mv9-v5v3 is a CWE-835 vulnerability in ryu. No vendor fix is recorded yet; mitigation options are listed below.

Ryu Infinite Loop vulnerability

Also known asCVE-2024-34487PYSEC-2026-1883

Published

May 5, 2024

Updated

Jul 7, 2026

Affected

1 pkg

Patched

None yet

Exploits

None indexed

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

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for GHSA-m9vm-8mv9-v5v3.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs51th percentile — riskier than 51% 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

🐍ryu

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

Description

OFPFlowStats in parser.py in Faucet SDN Ryu 4.34 allows attackers to cause a denial of service (infinite loop) via inst.length=0.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`ryu`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ryu, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of ryu has shipped for GHSA-m9vm-8mv9-v5v3 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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 GHSA-m9vm-8mv9-v5v3 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-m9vm-8mv9-v5v3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

`OFPFlowStats` in parser.py in Faucet SDN Ryu 4.34 allows attackers to cause a denial of service (infinite loop) via `inst.length=0`.

O3 Security · Impact-Aware SCA

Is GHSA-m9vm-8mv9-v5v3 in your dependencies?

O3 Security finds GHSA-m9vm-8mv9-v5v3 across PyPI 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