NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

Improper Privilege Management in NocoDBGHSA-fq4h-m3c8-8m2v

HIGHFix: nocodb/nocodb#2262

GHSA-fq4h-m3c8-8m2v is a high-severity (CVSS 8.8) Improper Privilege Management vulnerability in nocodb. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for nocodb — see the affected versions and patch details below.

Also known asCVE-2022-2063
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.4%probability of exploitation in next 30 days
Lower Risk+0.02%
Lower risk than most CVEs72th percentile — riskier than 72% of all scored CVEsHighest risk
0.57%1.01%1.45%1.89%1.1%1.4%May 26Sep 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

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.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
nocodbnpm
14Kdownloads / week

Description

Improper Privilege Management in GitHub repository nocodb/nocodb prior to 0.91.7+.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmnocodball versions0.91.8npm install nocodb@0.91.8

Affected Products

1 product · 1 configurations
Application
nocodbnocodb
< 0.91.7
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Improper Privilege Management in GitHub repository nocodb/nocodb prior t…

huntr.devNVDJun 2022

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update nocodb to 0.91.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fq4h-m3c8-8m2v is resolved across your whole dependency graph.

  3. Workarounds

    Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Frequently Asked Questions

Improper Privilege Management in GitHub repository nocodb/nocodb prior to 0.91.8.
O3 Security · Impact-Aware SCA

Is GHSA-fq4h-m3c8-8m2v in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Improper Privilege Management in NocoDB (High 8.8)