Snailsploit

#2484of 55,118
101Total CVSS
Vulnerabilities · 15
Medium
9
High
4
Critical
2
PT-2026-50491
5.3
2026-06-17
Vllm · Vllm · CVE-2026-54236
**Name of the Vulnerable Software and Affected Versions** vLLM versions prior to 0.23.1rc0 **Description** An incomplete fix for a previous memory leak issue allows unauthenticated attackers to leak heap memory addresses. The system fails to properly sanitize error messages in several response paths, echoing the string representation of exceptions directly to clients. This occurs because certain routes catch exceptions internally and construct responses themselves, bypassing the global sanitizing exception handler, while WebSocket frames bypass the handler chain entirely. Technical details include: - **API Endpoints**: 'POST /v1/messages' and 'POST /v1/messages/count tokens' within the Anthropic API router. - **Vulnerable Components**: The Server-Sent Events streaming converter in `vllm/entrypoints/anthropic/serving.py` and the realtime speech-to-text WebSocket in `vllm/entrypoints/speech to text/realtime/connection.py`. An attacker can exploit this by sending malformed image bytes through the Anthropic Messages API image content parts. This causes the `PIL.Image.open()` function to raise an `UnidentifiedImageError`, which includes a `BytesIO` object representation containing a verbatim heap memory address in the `error.message` field of the response body. **Recommendations** Update to version 0.23.1rc0 or later. As a temporary workaround, restrict access to the 'POST /v1/messages' and 'POST /v1/messages/count tokens' endpoints and the realtime speech-to-text WebSocket to minimize the risk of exploitation.
PT-2026-50129
6.8
2026-06-16
Git · Pydantic-Ai · CVE-2026-48782
Pydantic AI is a Python agent framework for building applications and workflows with Generative AI. In versions 1.56.0 through 1.101.0, 2.0.0b1, and 2.0.0b2, the cloud-metadata blocklist could be bypassed by encoding the metadata IP in an IPv6 transition form that the previous fix, CVE-2026-46678, did not decode, exposing cloud IAM short-term credentials. The previous remediation decoded only IPv4-mapped IPv6, 6to4, and the NAT64 well-known prefix, so the metadata guarantee did not hold for the remaining transition forms: IPv4-compatible IPv6 (::a.b.c.d), the NAT64 RFC 8215 local-use prefix (64:ff9b:1::/48), operator-chosen NAT64 prefixes, and ISATAP. The IPv6 wrapper is then delivered to the underlying IPv4 metadata endpoint. This occurs when an application using Pydantic AI opts a URL into force download='allow-local' (which disables the default block on private/internal IPs) and runs on a network that actually routes the affected IPv6 transition forms: NAT64-configured networks (IPv6-only or dual-stack-with-NAT64 deployments, including some Kubernetes setups) for the NAT64 variants, or networks with an ISATAP tunnel for ISATAP. A standard dual-stack cloud VM or container does not route these forms and is not affected in practice. The IPv4-compatible and Teredo variants are deprecated and addressed as defense-in-depth. This is an incomplete fix of GHSA-cqp8-fcvh-x7r3 / CVE-2026-46678 (itself a follow-up to CVE-2026-25580). This issue has been fixed in version 2.0.0b3.
PT-2026-37300
7.7
2026-05-05
Avideo · Avideo · CVE-2026-43884
**Name of the Vulnerable Software and Affected Versions** AVideo versions prior to 29.0 **Description** Two endpoints, 'plugin/AI/receiveAsync.json.php' and 'objects/EpgParser.php', use the `isSSRFSafeURL()` function to validate user-supplied URLs but then fetch them using `file get contents()` without disabling automatic redirect following. This allows an attacker to provide a URL that redirects to an internal or cloud-metadata address (such as 'http://169.254.169.254/latest/meta-data/'), bypassing SSRF protections because only the initial URL is validated. This can lead to the exfiltration of IAM credentials, instance identity, or access to internal services and port scanning. Additionally, several callers of `isSSRFSafeURL()` discard the `$resolvedIP` parameter intended for DNS pinning, making them susceptible to DNS rebinding TOCTOU (Time-of-Check to Time-of-Use) attacks. This occurs when a domain's DNS record changes between the time of validation and the time of the actual request. Affected callers include: - 'objects/aVideoEncoderReceiveImage.json.php' - 'objects/aVideoEncoder.json.php' - 'plugin/BulkEmbed/save.json.php' - 'plugin/AI/receiveAsync.json.php' - 'objects/EpgParser.php' - 'plugin/Scheduler/Scheduler.php' **Recommendations** Update AVideo to a version later than 29.0. As a temporary workaround, restrict access to the 'plugin/AI/receiveAsync.json.php' and 'objects/EpgParser.php' endpoints to minimize the risk of redirect-based SSRF.