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

GHSA-7xxh-373w-35vg

HIGH

GHSA-7xxh-373w-35vg is a high-severity (CVSS 8.5) SQL Injection vulnerability in payload. O3 Security confirms whether GHSA-7xxh-373w-35vg is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Payload has an SQL Injection via Query Handling

Also known asCVE-2026-34747
Published
Apr 1, 2026
Updated
Apr 6, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

payloadnpm
641Kdownloads / week

Description

Impact

Certain request inputs were not properly validated. An attacker could craft requests that influence SQL query execution, potentially exposing or modifying data in collections.

Patches

This issue has been fixed in v3.79.1 and later. Query input validation has been hardened.

Upgrade to v3.79.1 or later.

Workarounds

Until developers can upgrade:

  • Limit access to endpoints that accept dynamic query inputs to trusted users only.
  • Validate or sanitize input from untrusted clients before sending it to query endpoints.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmpayloadall versions3.79.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 payload. 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 payload to 3.79.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7xxh-373w-35vg 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-7xxh-373w-35vg 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-7xxh-373w-35vg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Certain request inputs were not properly validated. An attacker could craft requests that influence SQL query execution, potentially exposing or modifying data in collections. ### Patches This issue has been fixed in **v3.79.1** and later. Query input validation has been hardened. Upgrade to **v3.79.1 or later**. ### Workarounds Until developers can upgrade: - Limit access to endpoints that accept dynamic query inputs to trusted users only. - Validate or sanitize input from untrusted clients before sending it to query endpoints.
O3 Security · Impact-Aware SCA

Is GHSA-7xxh-373w-35vg in your dependencies?

O3 detects GHSA-7xxh-373w-35vg across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.