CVE-2025-67419
Evershop ≤ 2.1.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2025-67419 is a high-severity Excessive Platform Resource Consumption within a Loop (CWE-1050) vulnerability in Evershop Evershop. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 23th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SC-6 (Resource Availability) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-67419 is a Denial of Service (DoS) vulnerability in Evershop versions 2.1.0 and prior. The flaw occurs in the "GET /images" API endpoint, where the application processes SVG files without limiting the height of the use-element shadow tree or the dimensions of pattern tiles. This deficiency enables unbounded resource consumption on the application server, published on 2026-01-05 with a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) and mapped to CWE-1050.
Unauthenticated attackers can exploit this vulnerability remotely over the network with low attack complexity and no user interaction or privileges required. By sending a malicious request to the "GET /images" API containing a crafted SVG file, attackers can trigger excessive resource usage, exhausting the server's CPU or memory and causing a system-wide denial of service that disrupts availability for legitimate users.
Advisories and related resources are available at https://github.com/dos-m0nk3y/CVE/tree/main/CVE-2025-67419, which documents the issue, and the Evershop project repository at https://github.com/evershopcommerce/evershop.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-0799
Vulnerability Data
A Denial of Service (DoS) vulnerability in evershop 2.1.0 and prior allows unauthenticated attackers to exhaust the application server's resources via the "GET /images" API. The application fails to limit the height of the use-element shadow tree or the dimensions…
more
of pattern tiles during the processing of SVG files, resulting in unbounded resource consumption and system-wide denial of service.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 2 hardening rules · 2 OS baselines
V2.4.1V7.6.2V15.4.3V15.4.4
Mitigating Controls (NIST 800-53 r5) AI
SA-11 developer testing can discover loops that consume platform resources before deployment.
SC-6 directly protects resource availability by enforcing allocation limits that bound consumption from faulty loops.
AC-10 caps concurrent sessions, reducing blast radius when a loop consumes session or connection resources.
SC-5 limits effects of DoS events that can result from unbounded resource consumption inside loops.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Runtime monitoring can detect excessive resource use from loops as an adverse event.
Capacity monitoring and resource management directly limit impact of runaway consumption.
Secure SDLC practices can prevent introduction of unbounded loops during development.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Monitoring can alert on resource abuse but does not eliminate the coding flaw.
Security testing can discover the defect but does not remove it from production code.
Redundancy can absorb some resource spikes but does not prevent the loop defect.
Logging may detect excessive consumption but does not stop the loop.
Secure SDLC processes can catch the weakness during reviews but do not inherently prevent it.
Secure coding standards explicitly forbid resource-consuming loops.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 9 (1 rule)
- V-271709 OL 9 must be configured so that all network connections associated with SSH traffic terminate after becoming unresponsive. prevents CWE-1050
RHEL 9 (1 rule)
- V-257995 RHEL 9 must be configured so that all network connections associated with SSH traffic terminate after becoming unresponsive. prevents CWE-1050