Apache Struts, Remote Code Execution, CVE-2017-5638 (Critical)
The CVE-2017-5638 vulnerability in Apache Struts 2 stems from flawed error handling within the Jakarta Multipart parser. When a malicious
The CVE-2017-5638 vulnerability in Apache Struts 2 stems from flawed error handling within the Jakarta Multipart parser. When a malicious
How the CVE Works: The vulnerability exists in email address parsing libraries that fail to correctly handle RFC 5321/5322 standards
How the mentioned CVE works This CVE-2024-27115 exploits a weakness in the user creation module of the NovoSGA software. The
The vulnerability in ClearML arises from insufficient validation of symbolic and hard links within the `safe_extract` function during archive extraction.
The vulnerability in ZenML’s `PathMaterializer` class stems from an insufficient path validation mechanism during the extraction of a `data.tar.gz` archive.
The CVE-2025-53033 vulnerability in Liferay Portal arises from improper access control within the Freemarker template engine. Authenticated users can craft
The vulnerability exploits the insecure deserialization of messages between servers in a python-socketio multi-server setup. These deployments use a message
How the mentioned CVE works: The CVE-2017-5638 vulnerability resides in the Jakarta Multipart parser of Apache Struts. The exploit functions
How the mentioned CVE works: The CVE-2017-5638 vulnerability resides in the Jakarta Multipart parser of Apache Struts. The exploit is
The CVE-2024-34096 vulnerability is a DNS rebinding attack against the SillyTavern web UI. An attacker registers a domain name and
The vulnerability exists in the REST search endpoint’s `orderField` parameter, which is inserted directly into an HQL query without proper
How the mentioned CVE works: The CVE-2017-5638 vulnerability resides in the Jakarta Multipart parser of Apache Struts. The exploit functions
How the CVE Works: The vulnerability resides in the XWiki OIDC (OpenID Connect) authenticator. The token generation endpoint improperly checks
How the mentioned CVE works: The CVE-2021-33909 vulnerability, also known as “Sequoia,” exists in the Linux kernel’s filesystem layer. The
The vulnerability resides in the net/netfilter/x_tables.c component. It is a heap out-of-bounds write flaw in the `xt_compat_target_from_user` function. The issue
How the mentioned CVE works This vulnerability resides within the BI Publisher Integration component of Oracle Concurrent Processing. The flaw
The vulnerability exists in the nsCSSFrameConstructor::ContentAppended function within Firefox’s layout engine. When JavaScript appends multiple child nodes to a DOM
This CVE describes an elevation of privilege vulnerability in the Windows Common Log File System (CLFS) driver. The vulnerability arises
This vulnerability is a use-after-free condition triggered by Internet Explorer’s handling of specific Cascading Style Sheets (CSS) token sequences related
The vulnerability exists within the win32k.sys kernel-mode driver’s parsing of specially crafted TrueType font (TTF) files. When a malicious TTF
The CVE-2013-3918 vulnerability exists within the `InformationCardSigninHelper` ActiveX control (icardie.dll). The flaw is an out-of-bounds write memory corruption issue. When
How the mentioned CVE works: The CVE-2017-5638 vulnerability resides in the Jakarta Multipart parser of Apache Struts. The exploit is
The CVE-2017-5638 vulnerability in Apache Struts 2 stems from flawed error handling within the Jakarta Multipart parser. When a malicious
How the mentioned CVE works: The CVE-2017-5638 vulnerability exists in the Jakarta Multipart parser of Apache Struts. An attacker exploits
The vulnerability in FlowiseAI stems from the insecure handling of user input within the `convertToValidJSONString` function. When a POST request
How the mentioned CVE works: The CVE-2017-5638 vulnerability exists in the Jakarta Multipart parser of Apache Struts 2. An attacker
How the mentioned CVE works: The vulnerability is a stored Cross-Site Scripting (XSS) flaw within the application’s chat logging feature.
How the CVE Works: The vulnerability exists due to improper neutralization of user input in the FlowiseAI admin message viewing
How the mentioned CVE works: The CVE-2017-5638 vulnerability resides in the Jakarta Multipart parser of Apache Struts. The flaw is
How the mentioned CVE works: The CVE-2017-5638 vulnerability resides in the Jakarta Multipart parser of Apache Struts. The flaw is
How the CVE Works The vulnerability CVE-2024-41910 is a Stored Cross-Site Scripting (XSS) flaw in the NiceGUI framework. It originates
How the mentioned CVE works: The CVE-2017-5638 vulnerability resides in the Jakarta Multipart parser of Apache Struts. The exploit is
How the mentioned CVE works The vulnerability CVE-2024-31217 in FlowiseAI stems from insufficient sanitization of user input within chat components
The CVE-2025-11011 vulnerability in the `wrflib` Rust crate stems from a fundamental soundness issue within its `wrflib::byte_extract` module. All functions
How the mentioned CVE works: The CVE-2017-5638 vulnerability resides in the Jakarta Multipart parser of Apache Struts. The flaw is
How the mentioned CVE works: The CVE-2017-5638 vulnerability exists within the Jakarta Multipart parser in Apache Struts 2. The flaw
How the CVE Works CVE-2018-14717 is a critical vulnerability in Cloudflare’s reverse proxy logic. The flaw resided in the handling
How the mentioned CVE works: A use-after-free vulnerability exists in the `gsim` driver of the Android kernel. The issue occurs
The vulnerability CVE-2024-XXXX in phpMyFAQ stems from a fundamental flaw in the user registration logic where the application fails to
How the CVE Works: This vulnerability is a symlink-based permission bypass in Anthropic’s Claude Code. The security mechanism that enforces
The CVE-2017-5638 vulnerability in Apache Struts 2 stems from flawed error handling within the Jakarta Multipart parser. When a malicious
The CVE-2024-26924 vulnerability is a use-after-free flaw within the Linux kernel’s Netfilter subsystem, specifically in the nf_tables component. The bug
The CVE-2025-61735 vulnerability in Apache Kylin is a Server-Side Request Forgery (SSRF) flaw present in versions 4.0.0 through 5.0.2. The
The vulnerability exploits LXD’s API acceptance of `text/plain` and `application/x-www-form-urlencoded` Content-Types for JSON requests, bypassing CSRF protections. Client certificate authentication,
The vulnerability exists in LXD’s operations API endpoint (/1.0/operations). When queried, this API returns metadata for all running operations, which
The vulnerability exists in the LXD `/1.0/images` API endpoint, which is configured as an “AllowUntrusted” interface requiring no authentication. When
This CVE works by exploiting the Pongo2 template engine used in LXD’s snapshot naming feature. An attacker with instance configuration
The vulnerability exists in the `validLogFileName` function within `lxd/instance_logs.go` of LXD 5.0 LTS. This function validates log file names for
The vulnerability exists in the LXD image export API endpoint (/1.0/images/{fingerprint}/export). This endpoint uses a SQL `LIKE` clause for fingerprint
How the mentioned CVE works: This vulnerability is an authentication bypass using an alternate path or channel. In affected versions
The CVE-2024-33401 vulnerability in Apache Kylin stems from an improper access control mechanism within the application’s file-serving endpoints. Specifically, certain
The vulnerability in the DataChain library exists within the `loader.py` module. This module automatically reads and deserializes data from specific
This CVE is a flaw in the GNU Bash shell up to version 4.3. It stems from an incomplete fix
How the Mentioned CVE Works This vulnerability resides in the `libimagecodec.quram.so` library, a component responsible for processing image data on
How the mentioned CVE works: An unauthenticated attacker can exploit this vulnerability by sending a specially crafted serialized Java `SignedObject`
How the mentioned CVE works The vulnerability exists within the Meteobridge web interface, which is built using CGI scripts. A
The vulnerability CVE-2015-7755 is a critical authentication bypass in Juniper ScreenOS. The flaw resided in the code handling SSH and
How the mentioned CVE works: The vulnerability exists within the User module configuration, specifically in the handling of the ‘computed
The vulnerability resides in the `django.utils.archive.extract()` function, which is utilized by the `startapp –template` and `startproject –template` management commands. This
The vulnerability exists in the `/mpl//` endpoint within the `marimo/_server/main.py` source file. This endpoint is designed as an internal, unauthenticated
How the mentioned CVE works: The CVE-2025-22096 vulnerability exists within the Bulk User Import functionality of the Auth0 WordPress plugin.
How the mentioned CVE works: The CVE-2025-22093 vulnerability exists within the bulk user import functionality of the Auth0 Symfony SDK.
The vulnerability exists within the Bulk User Import functionality of the Auth0-PHP SDK. The affected endpoint fails to properly sanitize
How the mentioned CVE works: The CVE-2025-22033 vulnerability exists within the bulk user import functionality of the Auth0-PHP SDK. The
How the mentioned CVE works: The vulnerability exists in the user avatar upload feature of the Fiora chat application. The
The vulnerability exists in the `sys_read` system call handler within the RISC Zero zkVM guest platform. In affected versions, the
The CVE-2025-XXXXX vulnerability is a stored cross-site scripting (XSS) flaw within the Web Content translation feature of Liferay Portal and
This CVE-2025-22033 is a Cross-Site Scripting (XSS) vulnerability within the Fiora chat application’s user avatar handling mechanism. The vulnerability exists
The CVE-2025-XXXXX vulnerability is a buffer overflow within the NVMe-oF target component of SPDK (lib/nvmf). It occurs when processing an
The vulnerability in Apache Pyfory stems from its unsafe deserialization process. In affected versions, when Pyfory deserializes data, it can
How the mentioned CVE works: This CVE is an Insecure Direct Object Reference (IDOR) vulnerability within Liferay Portal’s audit event
The CVE-2025-XXXXX vulnerability in Finance.js v4.1.0 resides in the Internal Rate of Return (IRR) function. This financial function calculates the
The CVE-2025-XXXXX vulnerability in FormCMS v0.5.4 stems from a missing authentication check on the `/api/schemas/history/ ` API endpoint. This endpoint
The CVE-2025-????? vulnerability in the check-branches package stems from its insecure handling of user-supplied git branch names. The tool is
How the mentioned CVE works: The node-static package is designed to serve static files. When processing a client request for
How the Mentioned CVE Works The vulnerability CVE-2024-32017 is a Stored Cross-Site Scripting (XSS) flaw within Liferay’s web content management
The vulnerability exists in the `_merge()` function within the `merge.js` file. This function is used for recursively merging objects. A
The vulnerability in the MANTRA Chain’s `x/tokenfactory` module stems from a failure to properly enforce the transaction gas limit within
The mentioned CVE describes a reflected Cross-Site Scripting (XSS) vulnerability within Liferay Portal. The flaw exists in the handling of
The CVE describes a path traversal vulnerability within the ComboServlet component of Liferay Portal and DXP. This servlet is designed
How the mentioned CVE works: This Cross-Site Scripting (XSS) vulnerability exists within the Calendar widget of Liferay Portal and Liferay
How the Mentioned CVE Works The vulnerability CVE-2025-47130 is a stored cross-site scripting (XSS) flaw within Liferay Portal’s related asset
The CVE-2025-XXXXX vulnerability is a reflected Cross-Site Scripting (XSS) flaw within the page configuration functionality of Liferay Portal and Liferay
The vulnerability exists within the `affectedRevisionInfo` function in util/webhook/webhook.go. When a Gogs webhook push event is received at the unauthenticated
How the CVE Works The vulnerability exists within the code handling Azure DevOps webhook push events in Argo CD. When
How the CVE Works The vulnerability exists in the `util/db/repository_secrets.go` file, specifically within functions like secretToRepoCred. A race condition occurs
The vulnerability in the figma-developer-mcp server stems from the unsafe construction of a shell command using unsanitized user input. Within
The vulnerability in Coder AgentAPI prior to version 0.4.0 stems from insufficient validation of the `Origin` and `Host` HTTP headers
The vulnerability exists within the go-f3 library’s message validation logic. When processing a specifically crafted malicious “poison” F3 message, the
The CVE-31070 vulnerability operates within the justification verification caching mechanism of the go-f3 consensus library. The flaw stems from caching
The vulnerability exists within the `get_cache_dir()` function of the llama-index-core package, which insecurely uses a hardcoded, predictable directory path (/tmp/llama_index)
The vulnerability in minio-java versions before 8.6.0 stems from a flawed XML parsing mechanism. The library’s XML parser was configured
The vulnerability exists within the SNMP subsystem of Cisco IOS and IOS XE Software. A stack-based buffer overflow occurs when
How the CVE Works The vulnerability exists within the License Servlet of Fortra’s GoAnywhere MFT application. The servlet improperly handles
How the mentioned CVE works: The vulnerability exists in Adminer versions 4.0.0 to 4.7.8, specifically in the bundled `adminer.php` file
How the CVE Works The vulnerability in Libraesva ESG resides in its handling of compressed email attachments. The application inadequately
How the mentioned CVE works: The vulnerability exists in Sudo’s `–chroot` option. When this option is used, Sudo changes the
The vulnerability CVE-2024-32004 exists in the `j178/prek-action` due to unsafe handling of user-supplied inputs within a composite GitHub Action. A
The vulnerability in mkdocs-include-markdown-plugin stems from improper input validation when processing content for substitution placeholders. The plugin allows users to
The vulnerability exists within the `phonenumbers.Parse()` function of the github.com/nyaruka/phonenumbers library. This function is responsible for parsing a string input