radashi Allows Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
CVE-2025-48054GHSA-2xv9-ghh9-xc69
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (radashi 12.5.1), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm radashi
- Affected
- < 12.5.1
- Fixed in
- 12.5.1
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-2xv9-ghh9-xc69 lists affected ranges: npm radashi >=0 <12.5.1 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-2xv9-ghh9-xc69 lists affected ranges: npm radashi >=0 <12.5.1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 6.8 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N/E:U · score source
- EPSS
- CVE-2025-48054: 0.69% estimated exploitation activity in the next 30 days; percentile 52.97 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Impact This is a prototype pollution vulnerability. It impacts users of the set function within the Radashi library. If an attacker can control parts of the path argument to the set function, they could potentially modify the prototype of all objects in the JavaScript runtime, leading to unexpected behavior, denial of service, or even remote code execution in some specific scenarios. Patches The vulnerability has been patched in commit 8147abc8cfc3cfe9b9a17cd389076a5d97235a66. Users should upgrade to a version of Radashi that includes this commit. The fix utilizes a new helper function, isDangerousKey, to prevent the use of proto, prototype, or constructor as keys in the path, throwing an error if any are encountered. This check is bypassed for objects with a null prototype. Workarounds Users on older versions can mitigate this vulnerability by sanitizing the path argument provided to the set function to ensure that no part of the path string is proto, prototype, or constructor. For…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-2xv9-ghh9-xc69
- Revision 2 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 1 · created ·
Published from osv record GHSA-2xv9-ghh9-xc69
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2025-48054
Advisory: radashi Allows Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
IDs: CVE-2025-48054, GHSA-2xv9-ghh9-xc69
Record: https://patchnext.com/advisories/cve-2025-48054 (revision 3, source checked 26 Oct 2026, 12:37 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: radashi 12.5.1. A vendor fix does not mean a deployment is fixed.
## Affected components
- npm radashi: affected < 12.5.1; fixed in 12.5.1
## Suggested inspection (read-only)
- `npm ls radashi --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.
## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on radashi.
- Repeat the inspection and confirm that only fixed versions remain installed.
## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.
## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.
## Sources
- Verified: https://osv.dev/vulnerability/GHSA-2xv9-ghh9-xc69 (OSV record GHSA-2xv9-ghh9-xc69 lists affected ranges: npm radashi >=0 <12.5.1 (fixed))
- Verified: https://github.com/advisories/GHSA-2xv9-ghh9-xc69 (GitHub-reviewed advisory GHSA-2xv9-ghh9-xc69 lists affected ranges: npm radashi >=0 <12.5.1)
Commands are suggestions: review each one before running it.Loading voting…