CVE-2025-54884: DavidOsipov Vision-ui · Uncontrolled Resource Consumption
Affects DavidOsipov Vision-uiSource CVE Database V5
Not known to be exploited · CVSS 8.7 High : upgrade to 1.5.0 soon.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.5.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 5 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 26 Oct 2026.
What to do
Upgrade DavidOsipov Vision-ui to 1.5.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| DavidOsipov Vision-ui | Affected
| Fixed in
|
AI-suggested
1. Immediate upgrade to Vision UI version 1.5.0 or later, which contains the fix for this vulnerability, is the primary and most effective mitigation. 2. Implement input validation and rate limiting at the application or API gateway level to restrict the size of parameters passed to generateSecureId and getSecureRandomInt functions, preventing excessively large values that trigger resource exhaustion. 3. Deploy Web Application Firewalls (WAFs) with custom rules to detect and block anomalous requests with unusually large parameter values targeting these functions. 4. Monitor server resource usage (memory and CPU) closely for spikes or unusual patterns that may indicate exploitation attempts. 5. Use runtime application self-protection (RASP) tools to detect and mitigate resource exhaustion attacks in real time. 6. Conduct code audits and penetration testing focused on resource consumption vulnerabilities in custom modules or third-party dependencies. 7. Isolate critical services using containerization or microservice architectures to limit the blast radius of potential DoS attacks. 8. Educate development teams about secure coding practices related to resource allocation and input validation to prevent similar issues in future releases.
Description
Vision UI is a collection of enterprise-grade, dependency-free modules for modern web projects. In versions 1.4.0 and below, the generateSecureId and getSecureRandomInt functions in security-kit versions prior to 3.5.0 (packaged in Vision UI 1.4.0 and below) are vulnerable to Denial of Service (DoS) attacks. The generateSecureId(length) function directly used the length parameter to size a Uint8Array buffer, allowing attackers to exhaust server memory through repeated requests for large IDs since the previous 1024 limit was insufficient. The getSecureRandomInt(min, max) function calculated buffer size based on the range between min and max, where large ranges caused excessive memory allocation and CPU-intensive rejection-sampling loops that could hang the thread. This issue is fixed in version 1.5.0.