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

CVE-2022-3225 — @budibase/worker

HIGHFix: budibase/budibase@d35864b

CVE-2022-3225 is a high-severity (CVSS 8.8) CWE-913 vulnerability in @budibase/worker. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for @budibase/worker — see the affected versions and patch details below.

Improper Control of Dynamically-Managed Code Resources in budibase/budibase

Also known asGHSA-x92g-49gh-63qm
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
1 known
Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.0%probability of exploitation in next 30 days
Lower Risk+0.02%
Lower risk than most CVEs61th percentile — riskier than 61% of all scored CVEsHighest risk
0.00%0.49%0.97%1.46%0.4%1.0%Apr 26Aug 26Oct 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

3 pkgs affected

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

@budibase/workernpm
211downloads / week
@budibase/buildernpm
13downloads / week
@budibase/bbuinpm
3Kdownloads / week

Description

Improper Control of Dynamically-Managed Code Resources in GitHub repository budibase/budibase prior to 1.3.20.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
📦npm@budibase/workerall versions1.3.20npm install @budibase/worker@1.3.20
📦npm@budibase/builderall versions1.3.20npm install @budibase/builder@1.3.20
📦npm@budibase/bbuiall versions1.3.20npm install @budibase/bbui@1.3.20

Affected Products

1 product · 1 configurations
Application
budibasebudibase
< 1.3.20
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.

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update @budibase/worker to 1.3.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-3225 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

Improper Control of Dynamically-Managed Code Resources in GitHub repository budibase/budibase prior to 1.3.20.
O3 Security · Impact-Aware SCA

Is CVE-2022-3225 in your dependencies?

Find it across npm, including transitive dependencies.

CVE-2022-3225: @budibase/worker — Fixed in 1.3.20