CVE-2025-48054: radashi · Prototype Pollution
Affects radashiSource CVE Database V5
Not known to be exploited · CVSS 6.8 Medium : upgrade to 12.5.1 when convenient.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 12.5.1
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:UExploitation evidence
Disclosed: evidence found.
CVE published 27 May 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade radashi-org/radashi to 12.5.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubradashi-org/radashipkg:github/radashi-org/radashiOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations should immediately upgrade all Radashi dependencies to version 12.5.1 or later, where the vulnerability is patched. If immediate upgrade is not feasible, implement input validation and sanitization on all inputs that influence the 'path' argument in the 'set' function to explicitly disallow keys such as '__proto__', 'prototype', and 'constructor'. Conduct thorough code audits to identify any usage of the vulnerable 'set' function and assess exposure to untrusted inputs. Employ runtime application self-protection (RASP) or web application firewalls (WAFs) with custom rules to detect and block suspicious payloads attempting prototype pollution patterns. Integrate dependency scanning tools in CI/CD pipelines to detect vulnerable Radashi versions proactively. Additionally, monitor application logs and behavior for anomalies indicative of prototype pollution exploitation attempts. For organizations using third-party software that may embed Radashi, engage with vendors to confirm patch status or mitigation plans. Finally, educate development teams on secure coding practices related to prototype pollution and JavaScript object handling.
Description
Radashi is a TypeScript utility toolkit. Prior to version 12.5.1, the set function within the Radashi library is vulnerable to prototype pollution. 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. This issue has been patched in version 12.5.1. A workaround for this issue involves sanitizing the path argument provided to the set function to ensure that no part of the path string is __proto__, prototype, or constructor.