SvelteKit is a framework for rapidly developing robust, performant web applications using Svelte. Prior to 2.49.5, SvelteKit is vulnerable to a server side request forgery (SSRF) and denial of service (DoS) under certain conditions. From 2.44.0 through 2.49.4, the vulnerability results in a DoS when your app has at least one prerendered route (export const prerender = true). From 2.19.0 through 2.49.4, the vulnerability results in a DoS when your app has at least one prerendered route and you are using adapter-node without a configured ORIGIN environment variable, and you are not using a reverse proxy that implements Host header validation. This vulnerability is fixed in 2.49.5.
A vulnerability in the Linux kernel's IPv6 networking code (CVE-2025-71080) affects PREEMPT_RT kernels. It involves a race condition in the rt6_get_pcpu_route() function where a BUG_ON() can be triggered due to concurrent route installation attempts by multiple tasks on the same CPU. This bug has been fixed by handling the cmpxchg() failure gracefully and replacing BUG_ON with WARN_ON_ONCE for non-PREEMPT_RT kernels. The issue has a CVSS score of 7.5 (medium severity) and affects numerous Linux kernel versions, particularly those prior to certain 5.15.x and 6.x releases. A patch is available and should be applied to mitigate the issue.
A null pointer dereference vulnerability exists in the IPv4 code path of the Linux kernel's IP Virtual Server (IPVS) component. This occurs when processing packets in NAT mode with a misconfigured destination, leading to a crash due to dereferencing a NULL skb->dev pointer during route error handling. The issue arises from incomplete fixes in the error path that fail to properly set skb->dev before calling functions that dereference it.
CVE-2025-68800 is a use-after-free vulnerability in the Linux kernel's mlxsw spectrum_mr driver component. The flaw occurs when updating multicast route statistics due to a missing mutex lock during list entry deletion, which can lead to memory corruption. The issue has been fixed by adding a dedicated mutex to protect the multicast route list during updates.
AWS SDK for .NET works with Amazon Web Services to help build scalable solutions with Amazon S3, Amazon DynamoDB, Amazon Glacier, and more. From versions 4.0.0 to before 4.0.3.3, Customer applications could be configured to improperly route AWS API calls to non-existent or non-AWS hosts. This notification is related to the use of specific values for the region input field when calling AWS services. An actor with access to the environment in which the SDK is used could set the region input field to an invalid value. This issue has been patched in version 4.0.3.3.
React Router is a router for React. In @remix-run/server-runtime version prior to 2.17.3.and react-router 7.0.0 through 7.11.0, React Router (or Remix v2) is vulnerable to CSRF attacks on document POST requests to UI routes when using server-side route action handlers in Framework Mode, or when using React Server Actions in the new unstable RSC modes. There is no impact if Declarative Mode (<BrowserRouter>) or Data Mode (createBrowserRouter/<RouterProvider>) is being used. This issue has been patched in @remix-run/server-runtime version 2.17.3 and react-router version 7.12.0.
A vulnerability in the Linux kernel's IPv4 routing subsystem related to the sit driver was resolved. The flaw involved a race condition where a stale forwarding nexthop entry (fnhe) could be rebound to a new destination, causing a device reference count leak and warnings during network device unregistration. This issue could lead to resource leaks affecting system stability. The vulnerability has been fixed by clearing a key field to prevent reuse of stale entries.
Astro is a web framework. Prior to version 5.15.8, a mismatch exists between how Astro normalizes request paths for routing/rendering and how the application’s middleware reads the path for validation checks. Astro internally applies decodeURI() to determine which route to render, while the middleware uses context.url.pathname without applying the same normalization (decodeURI). This discrepancy may allow attackers to reach protected routes using encoded path variants that pass routing but bypass validation checks. This issue has been patched in version 5.15.8.
This post describes a method to detect BGP hijacking events by comparing BGP route announcements against authoritative IP/ASN mappings from IRR databases. The approach involves crawling live BGP stream data and flagging discrepancies where the originating ASN differs from the registered ASN in IRR data. While this is a detection technique rather than a direct threat or vulnerability, BGP hijacking itself poses significant risks to network confidentiality, integrity, and availability. European organizations relying on BGP for internet routing could be impacted by such attacks, especially critical infrastructure and large ISPs. The method described could help defenders identify suspicious route announcements quickly. However, the post is more of a community-shared detection approach than a report of an active exploit or vulnerability. Mitigation involves deploying real-time BGP monitoring, validating route origins with RPKI, and collaborating with regional internet registries. Countries with large internet exchange points and critical network infrastructure, such as Germany, the Netherlands, France, and the UK, are most likely to be affected by BGP hijacks. Given the nature of the content, the severity of the underlying threat (BGP hijacking) is high due to potential widespread impact and ease of exploitation by motivated attackers.
A server-side request forgery (SSRF) vulnerability exists in SimStudioAI sim affecting the file apps/sim/app/api/proxy/image/route.ts. This vulnerability allows remote attackers to manipulate server requests. The product uses a rolling release system, so specific affected versions are not disclosed. A patch identified by commit 3424a338b763115f0269b209e777608e4cd31785 is available and should be applied to resolve the issue. The vulnerability has a high severity score of 7.5 and public exploit code is available.
Quantum Route Redirect PhaaS is a high-severity phishing-as-a-service campaign targeting Microsoft 365 users globally. It leverages route redirection techniques to intercept and manipulate user traffic, aiming to harvest credentials or deliver malicious payloads. The threat exploits the widespread adoption of Microsoft 365, making it a significant risk for organizations relying on this platform. No known exploits in the wild have been confirmed yet, but the potential for credential theft and unauthorized access is substantial. European organizations using Microsoft 365 are at risk, especially those in countries with high Microsoft 365 market penetration and strategic importance. Mitigation requires advanced monitoring of network traffic, strict email filtering, and user awareness training focused on phishing and route manipulation tactics. Countries like Germany, the United Kingdom, France, and the Netherlands are likely to be most affected due to their extensive Microsoft 365 usage and critical infrastructure reliance. Given the ease of exploitation via phishing and the broad impact on confidentiality and integrity, the threat severity is assessed as high. Defenders should prioritize detection of anomalous routing behaviors and implement multi-factor authentication to reduce risk.
An Open Redirect vulnerability exists in the OAuth callback handler in file onlook/apps/web/client/src/app/auth/callback/route.ts in Onlook web application 0.2.32. The vulnerability occurs because the application trusts the X-Forwarded-Host header value without proper validation when constructing a redirect URL. A remote attacker can send a manipulated X-Forwarded-Host header to redirect an authenticated user to an arbitrary external website under their control, which can be exploited for phishing attacks.
lakeFS is an open-source tool that transforms object storage into a Git-like repositories. In versions 1.69.0 and below, missing authentication in the /api/v1/usage-report/summary endpoint allows anyone to retrieve aggregate API usage counts. While no sensitive data is disclosed, the endpoint may reveal information about service activity or uptime. This issue is fixed in version 1.71.0 . To workaround the vulnerability, use a load-balancer or application level firewall in order to block the request route /api/v1/usage-report/summary.
Directory traversal vulnerability in NextChat thru 2.16.0 due to the WebDAV proxy failing to canonicalize or reject dot path segments in its catch-all route, allowing attackers to gain sensitive information via authenticated or anonymous WebDAV endpoints.