How severe is GHSA-7gcm-g887-7qv7?

No CVSS score has been assigned to GHSA-7gcm-g887-7qv7 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-7gcm-g887-7qv7?

GHSA-7gcm-g887-7qv7 affects the following packages: protobuf (PyPI), protobuf (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-7gcm-g887-7qv7?

Update protobuf to 6.33.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7gcm-g887-7qv7 is resolved across your whole dependency graph.

How do I detect GHSA-7gcm-g887-7qv7 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for protobuf. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-7gcm-g887-7qv7 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-7gcm-g887-7qv7?

O3 pinpoints whether GHSA-7gcm-g887-7qv7 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-7gcm-g887-7qv7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-7gcm-g887-7qv7 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 type of vulnerability is GHSA-7gcm-g887-7qv7?

GHSA-7gcm-g887-7qv7 is classified as CWE-674 (CWE-674). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-7gcm-g887-7qv7 published, and has it been updated?

GHSA-7gcm-g887-7qv7 was published on January 23, 2026 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

GHSA-7gcm-g887-7qv7

GHSA-7gcm-g887-7qv7 is a CWE-674 vulnerability in protobuf. O3 Security confirms whether GHSA-7gcm-g887-7qv7 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

protobuf affected by a JSON recursion depth bypass

Also known asCVE-2026-0994PYSEC-2026-1805

Published

Jan 23, 2026

Updated

Jul 7, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Blast Radius

2 pkgs affected

🐍protobuf🐍protobuf

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

Due to missing recursion depth accounting inside the internal Any-handling logic, an attacker can supply deeply nested Any structures that bypass the intended recursion limit, eventually exhausting Python’s recursion stack and causing a RecursionError.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`protobuf`	≥ 6.30.0rc1&&< 6.33.5	6.33.5
🐍PyPI	`protobuf`	all versions	5.29.6

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for protobuf. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update protobuf to 6.33.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7gcm-g887-7qv7 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 pinpoints whether GHSA-7gcm-g887-7qv7 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-7gcm-g887-7qv7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A denial-of-service (DoS) vulnerability exists in google.protobuf.json_format.ParseDict() in Python, where the max_recursion_depth limit can be bypassed when parsing nested google.protobuf.Any messages. Due to missing recursion depth accounting inside the internal Any-handling logic, an attacker can supply deeply nested Any structures that bypass the intended recursion limit, eventually exhausting Python’s recursion stack and causing a RecursionError.

O3 Security · Impact-Aware SCA

Is GHSA-7gcm-g887-7qv7 in your dependencies?

O3 detects GHSA-7gcm-g887-7qv7 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works