CVE-2026-25545
HighSummary
Framework webowy Astro przed wersją 9.5.4 jest podatny na atak SSRF w przypadku stron renderowanych po stronie serwera, które zwracają błąd z niestandardową stroną błędu. Zmiana nagłówka `Host:` na serwer atakującego pozwala na przekierowanie do dowolnego wewnętrznego adresu URL i odczytanie odpowiedzi z pierwszego żądania.
Risk Assessment
Organizacja może być narażona na nieautoryzowany dostęp do wewnętrznych usług i danych, co może prowadzić do wycieku informacji lub kompromitacji systemów. Atakujący mogą uzyskać dostęp do metadanych chmurowych oraz interakcji z usługami w sieci wewnętrznej.
Recommendation
Zaleca się aktualizację do wersji 9.5.4 lub nowszej, aby usunąć tę podatność. Dodatkowo, warto wdrożyć walidację nagłówka `Host:` w aplikacji, aby zminimalizować ryzyko ataków SSRF.
Related vulnerabilities
- CVE-2026-91039Critical
Vulnerability in ash_authentication related to dynamic_oidc strategy that fails to maintain proper identity namespace separation across connections. An attacker controlling one connection can be signed in as a local user created through a different connection because user identities are not correctly separated.
- CVE-2026-86863Critical
In pgAdmin 4, the 'webserver' authentication source was vulnerable because WebserverAuthentication.get_user() fell back to reading the username directly from inbound HTTP request headers when the WSGI/CGI environment lookup returned nothing. As a result, any client able to reach pgAdmin could supply that header itself and authenticate as any username, including an existing Administrator, without a password. The issue affects versions from 6.2 before 9.18 and only applies when 'webserver' is enabled in AUTHENTICATION_SOURCES.
- CVE-2026-88952Critical
In ash_authentication there is an improper authentication vulnerability that allows an attacker to sign in as another user by linking their OAuth2 identity to an account that is not theirs. The attacker can attach a verified email to an account matched on other attributes, leading to session hijacking.
- CVE-2026-79752Critical
In CakePHP, the FunctionsBuilder methods (cast, extract, datePart, dateAdd) allow SQL injection by improperly handling user-controlled input. Untrusted data is incorporated into SQL syntax without proper escaping, potentially enabling attackers to execute arbitrary queries.
- CVE-2026-63472Critical
In Vendure, the createCustomerAndUser function in external authentication matches an existing customer by email address and attaches a new external authentication method without requiring verification. An attacker can use an unverified email to hijack the victim's account.
- CVE-2026-92960Critical
In vm2 before 3.11.6, the builtin: ['*'] configuration does not restrict access to os and dns builtins, allowing sandbox code to read host process identity and network topology. Attackers can use dns.setServers() to hijack the host process's DNS resolver globally.
- CVE-2026-92957Critical
In vm2 up to 3.11.6, NodeVM's require policy does not properly normalize node:-prefixed builtin specifiers, allowing bypass of denial lists. Sandbox code can access child_process module, enabling command execution on the host.
- CVE-2026-92956Critical
In vm2 versions 3.10.1 through 3.11.6, there is a sandbox escape via WebAssembly.compileStreaming and instantiateStreaming, allowing attackers to access the host process object on Node.js 26, leading to full host control.
- CVE-2026-92955Critical
In vm2 before 3.11.8, there is a sandbox escape vulnerability via console._stdout and console._stderr. Attackers can overwrite EventEmitter.prototype.emit and execute code on the host process, bypassing code generation restrictions.
- CVE-2026-92953Critical
In vm2 versions from 3.11.0 before 3.11.8, host TypedArray and ArrayBuffer prototypes are not protected from sandbox mutation. Attackers can modify prototypes, affecting host-created typed arrays and potentially leading to unauthorized actions.
Original NVD description (English source)
Astro is a web framework. Prior to version 9.5.4, Server-Side Rendered pages that return an error with a prerendered custom error page (eg. `404.astro` or `500.astro`) are vulnerable to SSRF. If the `Host:` header is changed to an attacker's server, it will be fetched on `/500.html` and they can redirect this to any internal URL to read the response body through the first request. An attacker who can access the application without `Host:` header validation (eg. through finding the origin IP behind a proxy, or just by default) can fetch their own server to redirect to any internal IP. With this they can fetch cloud metadata IPs and interact with services in the internal network or localhost. For this to be vulnerable, a common feature needs to be used, with direct access to the server (no proxies). Version 9.5.4 fixes the issue.

