CVE Catalog

A stack-based buffer overflow vulnerability has been identified in .NET Framework. This issue allows an unauthorized attacker to cause a denial-of-service condition over the network. The vulnerability affects multiple versions of .NET Framework, as well as Visual Studio 2022 and 2026. The root cause of the vulnerability is a stack-based buffer overflow, which can be exploited to disrupt service availability.

A vulnerability exists in .NET due to improper link resolution before file access, commonly referred to as 'link following'. This flaw allows an authorized attacker to manipulate files locally. The issue is present in .NET 8.0, 9.0, and 10.0, across Windows, Mac OS, and Linux platforms, as well as in Microsoft Visual Studio 2022 versions 17.12 and 17.14, and Visual Studio 2026 version 18.7.

A denial-of-service vulnerability has been identified in .NET and Microsoft Visual Studio. This issue arises from the unrestricted allocation of resources, which can be exploited by an unauthorized attacker to disrupt service over a network. The vulnerability affects .NET 8.0, 9.0, and 10.0, as well as Microsoft Visual Studio 2022 and 2026, across various operating systems including Windows, Linux, and Mac OS.

A denial-of-service vulnerability has been identified in .NET Framework, allowing an unauthorized attacker to disrupt service over a network. This issue arises from improper validation of certain types of input.

A vulnerability exists in the Symfony framework's UrlGenerator component, specifically in the doGenerate() method, prior to versions 5.4.53, 6.4.41, 7.4.13, and 8.0.13. The issue arises from improper handling of dot-segment encoding in URL generation, which can be exploited to manipulate route parameters. The encoding method used, strtr(), failed to correctly process chained '../' or './' segments, allowing attacker-controlled inputs to generate URLs that, after normalization according to RFC 3986, resolved to unintended paths. This flaw can disrupt route integrity, particularly when routes accept dots and slashes in parameters.

A vulnerability exists in the Symfony framework's HTML sanitizer component, specifically in the URL attribute sanitizer for certain HTML elements. In versions 6.1.0 prior to 6.4.41, 7.4.13, and 8.0.13, the sanitizer failed to properly handle URL-bearing attributes on <object>, <applet>, <iframe>, <img>, and <meta http-equiv="refresh"> elements. This oversight allowed URLs containing JavaScript payloads to bypass sanitization and be injected into the output, potentially leading to cross-site scripting (XSS) attacks. The issue arises when integrators explicitly allow these elements and attributes, enabling the injection of malicious URLs that are not properly sanitized.

A vulnerability exists in the Symfony framework's UrlSanitizer component, specifically in versions 6.1.0 prior to 6.4.41, 7.4.13, and 8.0.13. The issue arises because the UrlSanitizer::parse() method fails to properly reject percent-encoded Bidirectional (BiDi) formatting characters and uses an inadequate whitespace check. This oversight allows sanitized URLs to retain visual-spoofing characters, which can be decoded and displayed by downstream consumers, potentially leading to phishing or other security risks.

A vulnerability exists in the Symfony Mailer component's Mailomat webhook signature validation. The issue is present in Symfony versions 7.2 through 7.4.12 and 8.0 prior to 8.0.13. The vulnerability arises because the validation method parses the 'X-MOM-Webhook-Signature' header and allows the signature algorithm to be downgraded by passing the wire-supplied algorithm to the 'hash_hmac()' function. This could lead to the acceptance of weaker signature algorithms instead of enforcing Mailomat's required SHA-256 signature. The vulnerability could be exploited if an attacker can compute a signature using a less secure algorithm and send it in the webhook request.

A vulnerability exists in Symfony's HttpClient and HttpFoundation components, specifically in versions 5.4.0 prior to 5.4.53, 6.4.41, 7.4.13, and 8.0.13. The issue arises because the NoPrivateNetworkHttpClient component and the IpUtils::PRIVATE_SUBNETS constant fail to account for certain IPv6 transition prefixes, such as 6to4, NAT64, Teredo, and IPv4-compatible IPv6. This oversight allows attacker-controlled URLs to bypass private network restrictions and access private IPv4 targets, creating a server-side request forgery (SSRF) vulnerability.

A vulnerability in Symfony's DefaultAuthenticationFailureHandler component can lead to unauthorized access to protected GET routes. This issue affects Symfony versions prior to 5.4.53, 6.4.41, 7.4.13, and 8.0.13. When the failure_forward option is enabled, the handler incorrectly honors user-supplied _failure_path parameters. This allows an unauthenticated user to exploit failing login requests by dispatching subrequests to access control-protected routes, bypassing firewall listeners. As a result, GET endpoints in administrative areas can be accessed without authentication.

A stored cross-site scripting vulnerability has been identified in Adobe Commerce. This issue allows low-privileged attackers to inject malicious scripts into vulnerable form fields. When a victim accesses a page containing the compromised field, the injected JavaScript is executed in their browser. The vulnerability affects multiple versions of Adobe Commerce and Magento Open Source.

A vulnerability allowing improper restriction of XML external entity references (XXE) has been identified in Adobe Experience Manager (AEM). This vulnerability could lead to arbitrary code execution in the context of the current user. It affects AEM Cloud Service (CS) releases through 2026.5.0, as well as AEM 6.5 LTS Service Pack 1 and earlier, and AEM 6.5 Service Pack 24 and earlier. A low-privileged attacker could exploit this vulnerability to read sensitive files, potentially gaining elevated access or control over the victim's account or session. Notably, exploitation does not require user interaction.

A vulnerability allowing arbitrary code execution through improper encoding or escaping of output has been identified in Adobe Commerce. This issue affects several versions, including 2.4.9, 2.4.8-p5 and earlier, 2.4.7-p10 and earlier, 2.4.6-p15 and earlier, 2.4.5-p17 and earlier, and 2.4.4-p18 and earlier. The vulnerability also impacts Adobe Commerce B2B versions 1.5.3, 1.5.2-p5 and earlier, 1.4.2-p10 and earlier, 1.3.4-p17 and earlier, and 1.3.3-p18 and earlier. Additionally, it affects Magento Open Source versions 2.4.9, 2.4.8-p5 and earlier, 2.4.7-p10 and earlier, and 2.4.6-p15 and earlier. The vulnerability is present in Adobe Commerce Events versions 1.6.0 to 1.20.0. Exploitation of this vulnerability does not require user interaction and could result in arbitrary code execution in the context of the current user.

A vulnerability allowing unrestricted file uploads of dangerous types has been identified in Adobe Commerce. This issue could lead to arbitrary code execution in the context of the current user. An attacker might exploit this vulnerability to inject malicious scripts into a web page, potentially gaining elevated access or control over the victim's account or session. Exploitation requires user interaction, as a victim must visit a maliciously crafted URL or engage with a compromised web page.

A stored cross-site scripting vulnerability has been identified in Adobe Experience Manager (AEM) that allows low-privileged attackers to inject malicious scripts into vulnerable form fields. This could lead to the execution of malicious JavaScript in the browsers of users who visit the page containing the affected field. The vulnerability is present in multiple AEM products and versions, including AEM Cloud Service releases through 2026.5.0, AEM 6.5 LTS Service Pack 1 and earlier, and AEM 6.5 Service Pack 24 and earlier.

A path traversal vulnerability has been identified in Adobe Animate, specifically in the 2023 and 2024 versions prior to the latest updates. This vulnerability allows for arbitrary code execution within the context of the current user. An attacker could exploit this issue to access sensitive files or directories outside of the intended restrictions. However, exploitation requires user interaction, as a victim must open a malicious file.

A vulnerability in Adobe Animate related to incorrect authorization has been identified, which could allow arbitrary code execution in the context of the current user. This issue affects Adobe Animate 2023 versions through 23.0.15 and Adobe Animate 2024 versions through 24.0.13, on both Windows and macOS. The exploitation of this vulnerability does not require user interaction, but depends on conditions beyond the attacker's control.

A vulnerability has been identified in Adobe Animate, specifically in the 2023 version through 23.0.15 and the 2024 version through 24.0.13, on both Windows and macOS. This vulnerability arises from incorrect authorization, potentially allowing arbitrary code execution within the context of the current user. Exploitation requires user interaction, as a victim must open a malicious file.

A vulnerability allowing improper neutralization of special elements used in operating system commands has been identified in Adobe Animate. This OS command injection vulnerability could lead to arbitrary code execution within the context of the current user. The issue is present in Adobe Animate 2023 versions through 23.0.15 and in Adobe Animate 2024 versions through 24.0.13, on both Windows and macOS. Exploitation of this vulnerability requires user interaction, as a victim must open a malicious file.

A vulnerability has been identified in Adobe Animate, specifically in the 2023 and 2024 versions prior to the latest updates. This untrusted search path vulnerability could lead to arbitrary code execution within the context of the current user. Exploitation requires user interaction, as a victim must open a malicious file.

A vulnerability in Adobe Animate related to improper neutralization of special elements used in operating system commands has been identified. This OS command injection vulnerability could lead to arbitrary code execution within the context of the current user. Exploitation requires user interaction, as a victim must open a malicious file. The vulnerability affects Adobe Animate 2023 versions through 23.0.15 and Adobe Animate 2024 versions through 24.0.13 on both Windows and macOS.

A path traversal vulnerability has been identified in Adobe Experience Manager (AEM) that could lead to arbitrary file system read. This issue affects AEM Cloud Service (CS) Release 2026.5.0 and earlier, as well as AEM 6.5 LTS Service Pack 1 and earlier and AEM 6.5 Service Pack 24 and earlier. The vulnerability arises from improper limitations on pathname access, allowing attackers to read sensitive files and directories outside of the intended access scope. Exploitation of this vulnerability does not require user interaction.

A stored cross-site scripting vulnerability has been identified in Adobe Experience Manager (AEM) that allows low-privileged attackers to inject malicious scripts into vulnerable form fields. When a victim views the page containing the affected field, the injected JavaScript could be executed in their browser. This vulnerability is present in multiple AEM products and versions, including AEM Cloud Service releases through 2026.5.0, AEM 6.5 LTS Service Pack 1 and earlier, and AEM 6.5 Service Pack 24 and earlier.

A DOM-based Cross-Site Scripting vulnerability has been identified in Adobe Experience Manager (AEM) that allows attackers to execute malicious JavaScript in the context of the victim's browser. This vulnerability affects AEM Cloud Service (CS) Release 2026.5.0 and earlier, as well as AEM 6.5 LTS Service Pack 1 and earlier and AEM 6.5 Service Pack 24 and earlier. Exploitation requires user interaction, as the victim must visit a crafted webpage.

A DOM-based cross-site scripting vulnerability has been identified in Adobe Experience Manager (AEM) that allows attackers to execute malicious JavaScript in the context of the victim's browser. This vulnerability affects AEM Cloud Service (CS) Release 2026.5.0 and earlier, as well as AEM 6.5 LTS Service Pack 1 and earlier and AEM 6.5 Service Pack 24 and earlier. Exploitation requires user interaction, as the victim must visit a crafted webpage.

A DOM-based cross-site scripting vulnerability has been identified in Adobe Experience Manager (AEM) that allows attackers to execute malicious JavaScript in the context of the victim's browser. This issue affects AEM Cloud Service (CS) Release 2026.5.0 and earlier, as well as AEM 6.5 LTS Service Pack 1 and earlier and AEM 6.5 Service Pack 24 and earlier. Exploitation requires user interaction, as the victim must visit a crafted webpage.

A Server-Side Request Forgery (SSRF) vulnerability has been identified in Adobe Experience Manager (AEM) that could lead to arbitrary code execution in the context of the current user. This vulnerability affects AEM Cloud Service (CS) Release 2026.5.0 and earlier, as well as AEM 6.5 LTS Service Pack 1 and earlier and AEM 6.5 Service Pack 24 and earlier. A low-privileged attacker could exploit this vulnerability to make unauthorized server-side requests, potentially gaining elevated access or control over the victim's account or session. The exploitation of this vulnerability does not require user interaction.

A DOM-based Cross-Site Scripting vulnerability has been identified in Adobe Experience Manager (AEM) versions through 2026.5.0, 6.5 LTS Service Pack 1 and earlier, and 6.5 Service Pack 24 and earlier. This vulnerability allows an attacker to manipulate the DOM environment and execute malicious JavaScript in the context of the victim's browser. Exploitation requires user interaction, as the victim must visit a crafted webpage.

A DOM-based Cross-Site Scripting vulnerability has been identified in Adobe Experience Manager (AEM) that allows attackers to execute malicious JavaScript in the context of the victim's browser. This vulnerability affects AEM Cloud Service (CS) Release 2026.5.0 and earlier, as well as AEM 6.5 LTS Service Pack 1 and earlier and AEM 6.5 Service Pack 24 and earlier. Exploitation requires user interaction, as the victim must visit a crafted webpage.

A DOM-based Cross-Site Scripting (XSS) vulnerability has been identified in Adobe Experience Manager (AEM) that allows an attacker to execute malicious JavaScript in the context of the victim's browser. This vulnerability affects AEM Cloud Service (CS) Release 2026.5.0 and earlier, as well as AEM 6.5 LTS Service Pack 1 and earlier and AEM 6.5 Service Pack 24 and earlier. Exploitation requires user interaction, as the victim must visit a crafted webpage.

A DOM-based Cross-Site Scripting (XSS) vulnerability has been identified in Adobe Experience Manager (AEM) that allows an attacker to execute malicious JavaScript in the context of the victim's browser. This vulnerability affects AEM Cloud Service (CS) Release 2026.5.0 and earlier, as well as AEM 6.5 LTS Service Pack 1 and earlier and AEM 6.5 Service Pack 24 and earlier. Exploitation requires user interaction, as the victim must visit a crafted webpage.

A vulnerability in Adobe Experience Manager (AEM) related to missing authentication for critical functions could lead to a security feature bypass. This issue allows unauthorized write access. The vulnerability is present in AEM Cloud Service (CS) Release 2026.5.0 and earlier, as well as in AEM 6.5 LTS Service Pack 1 and earlier and AEM 6.5 Service Pack 24 and earlier. Exploitation of this vulnerability does not require user interaction.

A denial-of-service vulnerability has been identified in the @grpc/grpc-js package, which implements gRPC functionality in JavaScript without a C++ addon. This vulnerability affects versions prior to 1.9.16, as well as 1.10.0 through 1.10.12, 1.11.0 through 1.11.4, 1.12.0 through 1.12.7, 1.13.0 through 1.13.5, and 1.14.0 through 1.14.4. The issue arises when a client or server process receives an invalid incoming compressed message, leading to a crash.

A denial-of-service vulnerability has been identified in the @grpc/grpc-js package, affecting versions prior to 1.9.16, 1.10.0 through 1.10.12, 1.11.0 through 1.11.4, 1.12.0 through 1.12.7, 1.13.0 through 1.13.5, and 1.14.0 through 1.14.4. The issue arises when a server process created with @grpc/grpc-js encounters an invalid incoming HTTP/2 stream initiation, leading to a crash. This vulnerability impacts all servers using the @grpc/grpc-js package.

A denial-of-service vulnerability has been identified in Joi, a popular JavaScript schema description and data validation library. This issue affects versions of Joi prior to 17.13.4 and 18.2.1. The vulnerability arises when services validate user-supplied JSON or object input using recursive link schemas. If the validate() function is called without a try/catch block in a request handler, deeply nested input can cause an unhandled RangeError, potentially crashing the process. Although lower-impact validation paths using validateAsync() or a try/catch block are available, they still result in a RangeError instead of a properly structured ValidationError, complicating error handling.

An information exposure vulnerability has been identified in Adobe Commerce. This vulnerability could lead to a limited disclosure of sensitive information. Exploitation of this issue depends on conditions beyond the attacker's control and does not require user interaction.

A vulnerability allowing improper redirection (open redirect) has been identified in Adobe Commerce. This issue could lead to a security feature bypass, as it allows an attacker to create a malicious URL that redirects a victim to an attacker-controlled site. Such redirection could facilitate credential theft and account takeover. Exploitation of this vulnerability requires user interaction, as the victim must click on the malicious link. The vulnerability affects multiple versions of Adobe Commerce, Adobe Commerce B2B, Magento Open Source, and Adobe Commerce Events.

A stored cross-site scripting vulnerability has been identified in Adobe Commerce. This issue allows a high-privileged attacker to inject malicious scripts into vulnerable form fields. When a victim interacts with the page containing the compromised field, the injected JavaScript is executed in their browser. The vulnerability is present in several versions of Adobe Commerce and Magento Open Source.

A vulnerability has been identified in Adobe Commerce that involves incorrect authorization, potentially allowing for a security feature bypass. This issue could enable an attacker to circumvent security measures and gain unauthorized read access. The exploitation of this vulnerability depends on conditions beyond the attacker's control, and does not require user interaction. Affected versions include Adobe Commerce 2.4.9, 2.4.8-p5 and earlier, 2.4.7-p10 and earlier, 2.4.6-p15 and earlier, 2.4.5-p17 and earlier, 2.4.4-p18 and earlier, as well as Adobe Commerce B2B versions 1.5.3, 1.5.2-p5 and earlier, 1.4.2-p10 and earlier, 1.3.4-p17 and earlier, and 1.3.3-p18 and earlier.

A vulnerability allowing security feature bypass through incorrect authorization has been identified in Adobe Commerce. This issue could enable an attacker to gain unauthorized read access by bypassing security measures. The vulnerability affects multiple versions of Adobe Commerce, Magento Open Source, and Adobe Commerce B2B, as well as Adobe Commerce Events. Exploitation of this vulnerability does not require user interaction, but depends on conditions beyond the attacker's control.

A vulnerability has been identified in Adobe Commerce that involves incorrect authorization, potentially allowing a high-privileged attacker to bypass security measures and gain unauthorized read access. This vulnerability affects several versions of Adobe Commerce, Adobe Commerce B2B, and Magento Open Source. Notably, exploitation does not require user interaction.

A stored Cross-Site Scripting vulnerability has been identified in Adobe Commerce. This issue allows a high-privileged attacker to inject malicious scripts into vulnerable form fields. When a victim accesses the page containing the compromised field, the injected JavaScript could execute in their browser, potentially leading to unauthorized access or control over the victim's account or session. The vulnerability affects multiple versions of Adobe Commerce, including Adobe Commerce B2B and Magento Open Source.

A stored cross-site scripting vulnerability has been identified in Adobe Commerce. This issue allows low-privileged attackers to inject malicious scripts into vulnerable form fields. When a victim interacts with the page containing the compromised field, the injected JavaScript could execute in their browser, potentially leading to unauthorized access or control over the victim's account or session. The vulnerability is present in several versions of Adobe Commerce and Magento Open Source.

A SQL injection vulnerability has been identified in Adobe Commerce, specifically in versions 2.4.9, 2.4.8-p5 and earlier, 2.4.7-p10 and earlier, 2.4.6-p15 and earlier, 2.4.5-p17 and earlier, and 2.4.4-p18 and earlier. This vulnerability arises from improper neutralization of special elements used in SQL commands, potentially allowing high-privileged attackers to execute malicious SQL commands. Exploitation of this vulnerability could lead to arbitrary code execution in the context of the current user, with elevated access or control over the victim's account or session. Notably, this vulnerability does not require user interaction.

A vulnerability allowing incorrect authorization has been identified in Adobe Commerce. This issue could lead to a security feature bypass, allowing unauthorized read and write access. The vulnerability is present in Adobe Commerce versions 2.4.9, 2.4.8-p5 and earlier, 2.4.7-p10 and earlier, 2.4.6-p15 and earlier, 2.4.5-p17 and earlier, and 2.4.4-p18 and earlier. It also affects Adobe Commerce B2B versions 1.5.3, 1.5.2-p5 and earlier, 1.4.2-p10 and earlier, 1.3.4-p17 and earlier, and 1.3.3-p18 and earlier. Additionally, Magento Open Source versions 2.4.9, 2.4.8-p5 and earlier, 2.4.7-p10 and earlier, and 2.4.6-p15 and earlier are affected. The vulnerability exploitation does not require user interaction.

A vulnerability allowing security feature bypass through incorrect authorization has been identified in Adobe Commerce. This issue could enable an attacker to gain unauthorized read and write access. The vulnerability is present in multiple versions of Adobe Commerce, Adobe Commerce B2B, and Magento Open Source, as well as in Adobe Commerce Events versions 1.6.0 to 1.20.0. Exploitation of this vulnerability does not require user interaction.

A vulnerability in Puma, a Ruby/Rack web server, allows for source IP spoofing when PROXY protocol v1 is enabled and persistent connections are used. This issue affects Puma versions 5.5.0 prior to 7.2.1 and 8.0.2. The vulnerability arises because Puma incorrectly re-parses PROXY protocol headers after each keep-alive request on the same connection. An attacker could inject a second PROXY header, overwriting the REMOTE_ADDR variable. This misconfiguration can lead to security issues, as applications may rely on REMOTE_ADDR for security decisions, rate limiting, or auditing.

A vulnerability in the Puma web server, affecting versions 5.5.0 prior to 7.2.1 and 8.0.2, allows for remote memory exhaustion when PROXY protocol v1 support is enabled. The server reads incoming data into an internal buffer, waiting for a carriage return and line feed (CRLF) to identify PROXY v1 lines. An attacker can exploit this by sending bytes without CRLF, causing unbounded memory growth and increased CPU usage as the server scans the expanding buffer. This issue can lead to out-of-memory conditions or degraded availability.

A denial-of-service vulnerability has been identified in NVIDIA Triton Inference Server for Linux, versions 0.0 through 26.04. The issue arises from a missing release of memory after its effective lifetime, which an attacker can exploit to cause a denial-of-service condition.

An authentication bypass vulnerability has been identified in NVIDIA Triton Inference Server for Linux, affecting versions 0.0 through 26.04. This vulnerability allows attackers to bypass authentication through an alternative path or channel. Exploitation of this vulnerability could lead to unauthorized code execution, escalation of privileges, information disclosure, and data tampering.