How severe is CVE-2024-24786?

CVE-2024-24786 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

How do I fix CVE-2024-24786?

Update google.golang.org/protobuf to 1.33.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-24786 is resolved across your whole dependency graph.

How do I detect CVE-2024-24786 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for google.golang.org/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 CVE-2024-24786 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-2024-24786?

O3 pinpoints whether CVE-2024-24786 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 CVE-2024-24786 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-24786 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.

When was CVE-2024-24786 published, and has it been updated?

CVE-2024-24786 was published on March 5, 2024 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

CVE-2024-24786

HIGH

CVE-2024-24786 is a high-severity (CVSS 7.5) vulnerability in google.golang.org/protobuf. O3 Security confirms whether CVE-2024-24786 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Golang protojson.Unmarshal function infinite loop when unmarshaling certain forms of invalid JSON

Also known asGHSA-8r3f-844c-mc37GO-2024-2611

Published

Mar 5, 2024

Updated

Apr 10, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Blast Radius

3 pkgs affected

🐹google.golang.org/protobuf🐹google.golang.org/protobuf/encoding/protojson🐹google.golang.org/protobuf/internal/encoding/json

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

Description

The protojson.Unmarshal function can enter an infinite loop when unmarshaling certain forms of invalid JSON. This condition can occur when unmarshaling into a message which contains a google.protobuf.Any value, or when the UnmarshalOptions.DiscardUnknown option is set.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`google.golang.org/protobuf`	all versions	1.33.0
🐹Go	`google.golang.org/protobuf/encoding/protojson`	all versions	1.33.0
🐹Go	`google.golang.org/protobuf/internal/encoding/json`	all versions	1.33.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for google.golang.org/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 google.golang.org/protobuf to 1.33.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-24786 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 CVE-2024-24786 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 CVE-2024-24786. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2024-24786 in your dependencies?

O3 detects CVE-2024-24786 across Go 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