CVE-2025-66035
UnknownSummary
W Angularze, przed wersjami 19.2.16, 20.3.14 i 21.0.1, występowała luka związana z wyciekiem tokena XSRF poprzez URL-e względne protokołu w klientach HTTP. Luka ta prowadzi do nieautoryzowanego ujawnienia tokena XSRF do domeny kontrolowanej przez atakującego.
Risk Assessment
Organizacje mogą być narażone na ataki typu Cross-Site Request Forgery, co może prowadzić do nieautoryzowanego dostępu do danych użytkowników i operacji na ich kontach.
Recommendation
Zaleca się aktualizację Angulara do wersji 19.2.16, 20.3.14 lub 21.0.1. Alternatywnie, należy unikać używania URL-i względnych protokołu w żądaniach HttpClient i stosować ścieżki względne lub w pełni kwalifikowane, zaufane URL-e.
Related vulnerabilities
- CVE-2026-109157Critical
The TRENDnet TEW-432BRP router version 3.10B20 contains a stack-based buffer overflow in the formTcpipSetup function of /goform/formTcpipSetup. Manipulating the Name argument allows remote attack, and the exploit has been publicly disclosed.
- CVE-2026-63354Critical
Affected devices do not properly validate and sanitize visual marker data contained in imported CSV trace files before rendering it on the Trace page. An attacker can socially engineer an authorized user with the 'Read diagnostics' right into importing a crafted trace file.
- CVE-2026-63353Critical
Affected devices do not properly sanitize comment fields contained in imported trace files before rendering them on the Trace page. An attacker can socially engineer an authorized user with the 'Read diagnostics' right into importing a crafted trace file.
- CVE-2026-63350Critical
Affected devices do not properly restrict executable content contained in imported trace files. An attacker can socially engineer an authorized user with the 'Read diagnostics' right into importing a crafted trace file.
- CVE-2026-44415Critical
Affected systems do not properly restrict access to internal APIs and paths for authenticated users. An authenticated remote attacker could access sensitive internal information.
- CVE-2026-109110Critical
The Wavlink WL-WN592AX6 router version 250422 contains a vulnerability in the system function of the wmapd daemon component. Manipulation of an argument leads to OS command injection, and the attack can be launched remotely.
- CVE-2026-109109Critical
The Wavlink WL-WN530BE1-A router version 251117 contains a stack-based buffer overflow in the strcpy function of /cgi-bin/ExportAllSettings.cgi in the Settings Export CGI component. Manipulating the HTTP_COOKIE/X-Cmd argument allows remote attack.
- CVE-2026-109108Critical
The Wavlink WL-WN530BE1-A router version 251117 contains a vulnerability in the popen function of /cgi-bin/uploadVpn.cgi. Manipulating the Type argument leads to OS command injection, and the attack can be performed remotely.
- CVE-2026-108971Critical
A flaw has been found in D-Link DCS-930L B1.08B4 affecting the mpfd_decode function in bootloader_region.bin of the Emergency HTTP Recovery Server component. Manipulating the firmware argument leads to improper verification of the cryptographic signature. The attack can be performed remotely and the exploit has been published.
- CVE-2026-109758Critical
Perforce Helix Authentication Service (HAS) versions 2022.1-2025.2 retain a default SCIM bearer token that is not automatically replaced with a random value during installation. An attacker knowing this token can gain unauthorized access to the SCIM API and perform user and group operations. This issue can be chained with CVE-2026-61834, potentially leading to remote code execution.
Original NVD description (English source)
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. The vulnerability is a Credential Leak by App Logic that leads to the unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (http:// or https://) to determine if it is cross-origin. If the URL starts with protocol-relative URL (//), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the X-XSRF-TOKEN header. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS