Loading story…
A high-severity denial-of-service vulnerability, tracked as CVE-2026-16756, was disclosed in Amazon's Rust-based aws-smithy-http-server library. The flaw affects versions up to and including 0.66.4 and stems from the default serve() path accepting connections without effective limits, including missing connection and header-read timeouts and no cap on concurrent connections. An unauthenticated remote attacker can exploit the weakness with a Slowloris-style attack by holding many incomplete connections open until server sockets and async tasks are exhausted, causing service unavailability.
The issue is classified as CWE-770 and carries a high availability impact under CVSS v3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Reports say the vulnerable runtime used by generated servers can spawn unbounded work for incoming connections, enabling resource exhaustion and service immobilization. The recommended remediation is to upgrade to aws-smithy-http-server 0.66.5 or later, where bounded connection handling and explicit timeout controls, including header-read timeouts and semaphore-based concurrency limits, were introduced.
See affected versions and whether adversaries are exploiting it.
2 events from the most recent confirmed update back to the earliest known activity.
The references state that affected versions include releases up to 0.66.4 and recommend upgrading to 0.66.5 or later, with the remediation adding bounded connection handling and explicit timeout controls.
CVE-2026-16756 was disclosed for aws-smithy-http-server, describing an unauthenticated Slowloris-style denial-of-service issue in the default serve() path caused by missing timeouts and unbounded connection/task handling.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
cvereports.com
Open sourcecvefeed.io
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
InternLM's **LMDeploy** OpenAI-compatible API server is affected by **CVE-2026-63764**, a critical server-side request forgery flaw that lets unauthenticated attackers reach internal services by abusing image fetching in the `/v1/chat/completions` endpoint. The bug stems from validating only the initial `image_url` host and then following HTTP `302` redirects without re-checking whether subsequent destinations resolve to private or link-local addresses. As a result, an attacker can supply a public URL that redirects the server to targets such as `127.0.0.1` or the cloud metadata address `169.254.169.254`, potentially exposing internal-only applications and cloud IAM credentials. The vulnerability is tracked as **CWE-918** and has been rated **CVSS 9.2**; one affected build identified in public reporting is LMDeploy git version `648df3b`, while broader reporting says versions through **0.14.0** are impacted. A patch was merged to the main branch in **PR #4734**, but public reporting says no tagged release includes the fix yet. The issue was reportedly disclosed after a 36-day period without maintainer response following an initial report by researcher George Chen, increasing urgency for organizations running LMDeploy to review exposure and apply the upstream fix as soon as a release becomes available.
Jul 22, 2026
**LoLLMs WEBUI** was found to contain two high-severity vulnerabilities affecting core web application functionality. The most severe issue, tracked as `CVE-2026-33340`, is an **unauthenticated server-side request forgery (SSRF)** in the `POST /api/proxy` endpoint that affects all known existing versions. An attacker can abuse the endpoint to force the server to make arbitrary `GET` requests, potentially reaching internal services, scanning local networks, and retrieving sensitive cloud metadata, including possible AWS or GCP IAM tokens. The flaw is mapped to `CWE-306` and `CWE-918`, with a `CVSS 3.1` vector of `AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`, and no patched version was known at publication. A second critical flaw, `CVE-2026-0562`, affects **parisneo/lollms** through an **insecure direct object reference (IDOR)** in friend request handling. In versions up to `2.2.0`, the `respond_request()` function in `backend/routers/friends.py` failed to verify that the authenticated user was part of the targeted friendship, allowing any logged-in user to accept or reject another user's friend requests via `/api/friends/requests/{friendship_id}`. The weakness, mapped to `CWE-863`, could enable unauthorized actions, privacy violations, and social engineering abuse; unlike the SSRF issue, this bug includes references to a fixing commit and a Huntr report.
Jun 29, 2026
Researchers publicly disclosed **HTTP/2 Bomb**, a remote denial-of-service technique that abuses standard HTTP/2 behavior to rapidly exhaust memory on major web servers and proxies, including **nginx, Apache HTTP Server, Microsoft IIS, Envoy, and Cloudflare Pingora**. The attack combines **HPACK header-compression amplification** with a **Slowloris-style flow-control stall**, letting a low-bandwidth client trigger disproportionate server-side allocations and keep that memory pinned by advertising a zero-byte window. Reports said a single machine on a 100 Mbps connection could make vulnerable services inaccessible within seconds, with testing showing **Apache httpd** and **Envoy** consuming roughly **32 GB of RAM** in about **10 to 20 seconds** under default HTTP/2 configurations. Public disclosures and proof-of-concept code indicated the amplification largely comes from per-header bookkeeping rather than oversized decoded header values, allowing common decoded-size limits to be bypassed. **Apache** tracked its exposure as **`CVE-2026-49975`** and released a fix in **`mod_http2 2.0.41`**, while **nginx** addressed the issue in **`1.29.8`**; advisories initially said **IIS, Envoy, and Pingora** lacked patches, though later disclosures showed **Envoy** assigned **`CVE-2026-47774`** and published an advisory. Researchers estimated more than **880,000** internet-exposed HTTP/2 systems could be affected and recommended upgrading where fixes exist, or otherwise disabling HTTP/2, enforcing strict header-count limits, and monitoring for abnormal memory growth.
Jul 20, 2026