Loading story…
A high-severity server-side request forgery flaw tracked as CVE-2026-63306 affects stoatchat versions before 0.13.5, allowing unauthenticated attackers to abuse the /proxy and /embed endpoints with arbitrary URLs. The vulnerable endpoints reportedly lack DNS resolution filtering and private IP range validation, enabling requests to be routed toward internal network resources that should not be externally reachable.
The issue can be used to enumerate internal services, fingerprint internal applications, and access cloud instance metadata endpoints, including by chaining redirects to reach otherwise restricted infrastructure. The vulnerability is classified as CWE-918 and carries a CVSS v3.1 vector of AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N; advisory data also indicates proof-of-concept exploitation and automatable attack potential. Version 0.13.5 is listed as unaffected.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
2 events from the most recent confirmed update back to the earliest known activity.
The CVE record for CVE-2026-63306 was updated on 2026-07-16 with references, affected-version information, CVSS data, and SSVC metadata. The update indicated proof-of-concept exploitation and automatable attack potential, and noted that version 0.13.5 is unaffected.
A disclosure described an unauthenticated SSRF flaw in stoatchat affecting versions before 0.13.5 via the /proxy and /embed endpoints, which accept arbitrary URLs without DNS filtering or private IP validation. The issue can enable internal service enumeration, application fingerprinting, and access to cloud metadata endpoints, including through redirect chains.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
2 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourcevulncheck.com
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.
Postiz, an AI social media scheduling tool, patched two **server-side request forgery** vulnerabilities affecting its public stream functionality. `CVE-2026-34577` exposed an unauthenticated flaw in `GET /public/stream`, where a user-controlled `url` parameter could cause the server to fetch and return the full HTTP response to the requester. The endpoint relied on an extension check requiring the URL to end in `mp4`, but that validation could be trivially bypassed, enabling access to internal services, cloud metadata endpoints, and other internal network resources. The issue was fixed in version **2.21.3** and assigned **CWE-918**.
Jun 29, 2026
Datadog Security Labs detailed **CVE-2020-8561**, an unpatchable Kubernetes weakness that can turn the `kube-apiserver` into a high-impact server-side request forgery (**SSRF**) proxy. An attacker with valid Kubernetes credentials and elevated privileges, typically `cluster-admin`, can abuse a `ValidatingWebhookConfiguration` object to make the API server send requests to attacker-controlled or internal destinations. By combining that behavior with profiling-enabled log-level changes, the attacker can cause the API server to log full responses from those privileged network requests rather than merely confirming whether a port is reachable. The issue is most dangerous when the Kubernetes control plane sits in a more trusted network segment than worker nodes, including managed Kubernetes environments hosted inside cloud provider networks. Because there is no straightforward code fix, defenders are being urged to reduce exposure through configuration and architecture changes, notably disabling API server profiling with: ```bash --profiling=false ``` and ensuring that SSRF originating from the API server cannot reach sensitive internal services or metadata endpoints.
Jun 29, 2026
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