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

CVE-2023-5573 — @vrite/sdk

MEDIUMFix: vriteio/vrite@1877683

CVE-2023-5573 is a medium-severity (CVSS 4.7) CWE-770 vulnerability in @vrite/sdk. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for @vrite/sdk — see the affected versions and patch details below.

Allocation of Resources Without Limits or Throttling in vriteio/vrite

Also known asGHSA-5ghm-h2wq-g3mh
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Oct 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-5573.

EPSS Exploitation Probability

via FIRST.org ↗
0.6%probability of exploitation in next 30 days
Lower Risk+0.10%
Lower risk than most CVEs51th percentile — riskier than 51% of all scored CVEsHighest risk
0.00%0.38%0.76%1.15%0.0%0.6%May 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

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.

1other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
@vrite/sdknpm
380downloads / week

Description

Allocation of Resources Without Limits or Throttling in GitHub repository vriteio/vrite prior to 0.3.0.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npm@vrite/sdkall versions0.3.0npm install @vrite/sdk@0.3.0

Affected Products

1 product · 1 configurations
Application
vritevrite
< 0.3.0
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.

Allocation of Resources Without Limits or Throttling in GitHub repositor…

huntr.devNVDOct 2023

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update @vrite/sdk to 0.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-5573 is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

Allocation of Resources Without Limits or Throttling in GitHub repository vriteio/vrite prior to 0.3.0.
O3 Security · Impact-Aware SCA

Is CVE-2023-5573 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2023-5573: @vrite/sdk — Fixed in 0.3.0