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

CVE-2024-57083 redoc

HIGHFix: Redocly/redoc#2638

CVE-2024-57083 is a high-severity (CVSS 7.5) CWE-1321 vulnerability in redoc. A fix is available for redoc — see the affected versions and patch details below.

Redoc Prototype Pollution via `Module.mergeObjects` Component

Also known asGHSA-9rhg-254w-fh9x
Published
Mar 28, 2025
Updated
Aug 12, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Sep 22, 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.
  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-57083.

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs44th percentile — riskier than 44% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2024-57083 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

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.

67other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
redocnpm
942Kdownloads / week

Description

A prototype pollution in the component Module.mergeObjects (redoc/bundles/redoc.lib.js:2) of redoc <= 2.2.0 allows attackers to cause a Denial of Service (DoS) via supplying a crafted payload.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmredocall versions2.4.0npm install redoc@2.4.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update redoc to 2.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-57083 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-57083 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2024-57083. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This vulnerability is rated as an Important severity because it allows attackers to exploit a prototype pollution issue in the Module.mergeObjects method by crafting a malicious payload. An attacker can alter the built-in Object.prototype, causing a Denial of Service (DoS) condition, leading to system instability,…

ProductFixed inAdvisory
Red Hat Advanced Cluster Security 4.5advanced-cluster-security/rhacs-central-db-rhel8:4.5.9-1RHSA-2025:3928
Red Hat Advanced Cluster Security 4.6advanced-cluster-security/rhacs-central-db-rhel8:4.6.5-1RHSA-2025:3929
Red Hat Advanced Cluster Security 4.7advanced-cluster-security/rhacs-central-db-rhel8:4.7.2-2RHSA-2025:3930
Red Hat OpenShift GitOps 1.14openshift-gitops-1/argocd-rhel8:v1.14.4-1RHSA-2025:8274
Red Hat OpenShift GitOps 1.15openshift-gitops-1/argocd-extensions-rhel8:v1.15.2-4RHSA-2025:7753

Frequently Asked Questions

A prototype pollution in the component Module.mergeObjects (redoc/bundles/redoc.lib.js:2) of redoc <= 2.2.0 allows attackers to cause a Denial of Service (DoS) via supplying a crafted payload.
O3 Security · Impact-Aware SCA

Is CVE-2024-57083 in your dependencies?

O3 Security finds CVE-2024-57083 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2024-57083: redoc DoS (High 7.5) | O3 Security