Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

GHSA-j452-xhg8-qg39

MEDIUMFix: mafintosh/protocol-buffers-schema#70

GHSA-j452-xhg8-qg39 is a medium-severity (CVSS 6.5) remote code execution vulnerability in protocol-buffers-schema. O3 Security confirms whether GHSA-j452-xhg8-qg39 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Mafintosh's protocol-buffers-schema is vulnerable to prototype pollution

Also known asCVE-2026-5758
Published
Apr 15, 2026
Updated
May 5, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

protocol-buffers-schemanpm
7.3Mdownloads / week

Description

JavaScript is vulnerable to prototype pollution in Mafintosh's protocol-buffers-schema Version 3.6.0, where an attacker may alter the application logic, bypass security checks, cause a DoS or achieve remote code execution.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmprotocol-buffers-schemaall versions3.6.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for protocol-buffers-schema. 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.

  2. Fix

    Update protocol-buffers-schema to 3.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j452-xhg8-qg39 is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-j452-xhg8-qg39 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-j452-xhg8-qg39. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

JavaScript is vulnerable to prototype pollution in Mafintosh's protocol-buffers-schema Version 3.6.0, where an attacker may alter the application logic, bypass security checks, cause a DoS or achieve remote code execution.
O3 Security · Impact-Aware SCA

Is GHSA-j452-xhg8-qg39 in your dependencies?

O3 detects GHSA-j452-xhg8-qg39 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.