CWE hub

CWE-413 vulnerabilities

This hub groups CVEs that NVD maps to CWE-413, so you can review recent disclosures, common vendors, and related weakness patterns in one place.

RSS View CWE-413 on MITRE

Definition mirrored from MITRE CWE (MITRE CWE 4.13). CVE list is sourced live from NVD.

Mapped CVEs

Records currently returned for this weakness id.

Top vendor

pterodactyl

1 mapped CVEs in the aggregate scan.

Weakness roll-up for CWE-413

Showing 1-2 of 2 vulnerabilities.

CWE: CWE-413

Sort current page

CVE-2026-32748HighCVSS8.7Published Mar 26, 2026

Squid is a caching proxy for the Web. Prior to version 7.5, due to premature release of resource during expected lifetime and heap Use-After-Free bugs, Squid is vulnerable to Denial of Service when handling ICP traffic. This problem allows a remote attacker to perform a reliable and repeatable Denial of Service attack against the Squid service using ICP protocol. This attack is limited to Squid deployments that explicitly enable ICP support (i.e. configure non-zero `icp_port`). This problem _cannot_ be mitigated by denying ICP queries using `icp_access` rules. This bug is fixed in Squid version 7.5.

Affected vendor

squid-cache

Affected product

squid

Coverage

Single affected product entry

CVSS

8.7

HIGH

Published

Mar 26, 2026

CVE-2025-69198MediumCVSS6.0Published Jan 19, 2026

Pterodactyl is a free, open-source game server management panel. Pterodactyl implements rate limits that are applied to the total number of resources (e.g. databases, port allocations, or backups) that can exist for an individual server. These resource limits are applied on a per-server basis, and validated during the request cycle. However, in versions prior to 1.12.0, it is possible for a malicious user to send a massive volume of requests at the same time that would create more resources than the server is allotted. This is because the validation occurs early in the request cycle and does not lock the target resource while it is processing. As a result sending a large volume of requests at the same time would lead all of those requests to validate as not using any of the target resources, and then all creating the resources at the same time. As a result a server would be able to create more databases, allocations, or backups than configured. A malicious user is able to deny resources to other users on the system, and may be able to excessively consume the limited allocations for a node, or fill up backup space faster than is allowed by the system. Version 1.12.0 fixes the issue.