Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
CRITICAL severity

Validation Bypass in schema-inspectorGHSA-r24h-634p-m72x

CRITICALFix: Atinux/schema-inspector@345a7b2

GHSA-r24h-634p-m72x is a critical-severity (CVSS 9.8) CWE-668 vulnerability in schema-inspector. A fix is available for schema-inspector — see the affected versions and patch details below.

Also known asCVE-2019-10781SNYK-JS-SCHEMAINSPECTOR-536970
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 12, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs72th percentile — riskier than 72% of all scored CVEsHighest risk
0.00%0.63%1.26%1.89%0.1%1.4%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-r24h-634p-m72x by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

113other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
schema-inspectornpm
82Kdownloads / week

Description

In schema-inspector before 1.6.9, a maliciously crafted JavaScript object can bypass the sanitize() and the validate() function used within schema-inspector.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmschema-inspectorall versions1.6.9npm install schema-inspector@1.6.9

Affected Products

1 product · 1 configurations
Application
schema-inspectorschema-inspector_project
< 1.6.9
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update schema-inspector to 1.6.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r24h-634p-m72x 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.

Frequently Asked Questions

In schema-inspector before 1.6.9, a maliciously crafted JavaScript object can bypass the `sanitize()` and the `validate()` function used within schema-inspector.
O3 Security · Impact-Aware SCA

Is GHSA-r24h-634p-m72x in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Validation Bypass in schema-inspector (Critical 9.8)