CVE-2025-55346: JFROG · Code Injection
Source CVE Database V5
Not known to be exploited · 22% EPSS · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 22.3% chance of exploitation in 30 days – higher than 97% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 14 Aug 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 2026-10-26.
What to do
AI-suggested
To mitigate CVE-2025-55346, European organizations should immediately audit their codebases and dependencies for unsafe usage of dynamic Function constructors or similar code generation methods that incorporate user input. Replace dynamic Function constructors with safer alternatives such as static code or well-validated input parsing. Implement strict input validation and sanitization to ensure no untrusted data reaches code evaluation functions. Employ Content Security Policy (CSP) headers to restrict execution of inline scripts and reduce the impact of injected code. Use runtime application self-protection (RASP) tools to detect and block suspicious code execution patterns. Regularly update and patch all JavaScript frameworks and libraries once vendors release fixes. Conduct penetration testing focused on code injection vectors. Additionally, implement network-level protections such as Web Application Firewalls (WAFs) with rules targeting suspicious POST requests containing executable code patterns. Finally, establish monitoring and alerting for anomalous JavaScript execution or unexpected outbound connections that may indicate exploitation attempts.
Description
User-controlled input flows to an unsafe implementation of a dynamic Function constructor, allowing network attackers to run arbitrary unsandboxed JS code in the context of the host, by sending a simple POST request.