CVE-2026-8161 Vulnerability Analysis & Exploit Details

CVE-2026-8161
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2026-8161 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-8161 Details

Status: Analyzed

Last updated: 🕝 13 May 2026, 14:43 UTC
Originally published on: 🕙 12 May 2026, 10:16 UTC

Time between publication and last update: 1 days

CVSS Release: version 3

CVSS3 Source

ce714d77-add3-4f53-aff5-83d477b104bb

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CVE-2026-8161 Vulnerability Summary

CVE-2026-8161: multiparty@4.2.3 and lower versions are vulnerable to denial of service via uncaught exception. By sending a multipart/form-data request with a field name that collides with an inherited Object.prototype property such as __proto__, constructor, or toString, the parser invokes .push() on the inherited prototype value rather than an array, throwing a TypeError that propagates as an uncaught exception and crashes the process. Impact: any service accepting multipart uploads via multiparty is affected. Workarounds: none. Upgrade to multiparty@4.3.0 or higher.

Assessing the Risk of CVE-2026-8161

Access Complexity Graph

The exploitability of CVE-2026-8161 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-8161

With low attack complexity and no required privileges, CVE-2026-8161 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-8161, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-8161, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2026-8161 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2026-8161 poses no threat to data integrity.
  • Availability: High
    CVE-2026-8161 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2026-8161 References

External References

CWE Common Weakness Enumeration

CWE-1321

CAPEC Common Attack Pattern Enumeration and Classification

  • Accessing Functionality Not Properly Constrained by ACLs CAPEC-1 In applications, particularly web applications, access to functionality is mitigated by an authorization framework. This framework maps Access Control Lists (ACLs) to elements of the application's functionality; particularly URL's for web apps. In the case that the administrator failed to specify an ACL for a particular element, an attacker may be able to access it with impunity. An attacker with the ability to access functionality not properly constrained by ACLs can obtain sensitive information and possibly compromise the entire application. Such an attacker can access resources that must be available only to users at a higher privilege level, can access management sections of the application, or can run queries for data that they otherwise not supposed to.
  • Exploiting Incorrectly Configured Access Control Security Levels CAPEC-180 An attacker exploits a weakness in the configuration of access controls and is able to bypass the intended protection that these measures guard against and thereby obtain unauthorized access to the system or network. Sensitive functionality should always be protected with access controls. However configuring all but the most trivial access control systems can be very complicated and there are many opportunities for mistakes. If an attacker can learn of incorrectly configured access security settings, they may be able to exploit this in an attack.
  • Manipulating User-Controlled Variables CAPEC-77 This attack targets user controlled variables (DEBUG=1, PHP Globals, and So Forth). An adversary can override variables leveraging user-supplied, untrusted query variables directly used on the application server without any data sanitization. In extreme cases, the adversary can change variables controlling the business logic of the application. For instance, in languages like PHP, a number of poorly set default configurations may allow the user to override variables.

Vulnerable Configurations

  • cpe:2.3:a:pillarjs:multiparty:0.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:0.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:0.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:0.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:0.3.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:0.3.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:0.4.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:0.4.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:0.5.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:0.5.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:0.6.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:0.6.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:0.7.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:0.7.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:0.8.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:0.8.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:0.9.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:0.9.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:0.9.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:0.9.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:0.9.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:0.9.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:0.9.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:0.9.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:0.9.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:0.9.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:0.9.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:0.9.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:0.9.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:0.9.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:0.9.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:0.9.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:0.9.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:0.9.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:0.9.9:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:0.9.9:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:0.9.10:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:0.9.10:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:0.9.11:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:0.9.11:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:1.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:1.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:1.0.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:1.0.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:1.0.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:1.0.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:1.0.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:1.0.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:1.0.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:1.0.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:1.0.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:1.0.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:1.0.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:1.0.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:1.0.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:1.0.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:1.0.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:1.0.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:1.0.9:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:1.0.9:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:1.0.10:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:1.0.10:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:1.0.11:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:1.0.11:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:2.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:2.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:2.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:2.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:2.1.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:2.1.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:2.1.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:2.1.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:2.1.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:2.1.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:2.1.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:2.1.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:2.1.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:2.1.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:2.1.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:2.1.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:2.1.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:2.1.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:2.1.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:2.1.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:2.1.9:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:2.1.9:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:2.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:2.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:3.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:3.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:3.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:3.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:3.1.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:3.1.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:3.1.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:3.1.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:3.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:3.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:3.2.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:3.2.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:3.2.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:3.2.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:3.2.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:3.2.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:3.2.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:3.2.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:3.2.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:3.2.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:3.2.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:3.2.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:3.2.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:3.2.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:3.2.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:3.2.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:3.2.9:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:3.2.9:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:3.2.10:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:3.2.10:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:3.3.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:3.3.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:3.3.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:3.3.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:3.3.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:3.3.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:4.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:4.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:4.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:4.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:4.1.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:4.1.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:4.1.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:4.1.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:4.1.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:4.1.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:4.1.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:4.1.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:4.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:4.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:4.2.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:4.2.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:4.2.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:4.2.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:pillarjs:multiparty:4.2.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:pillarjs:multiparty:4.2.3:*:*:*:*:node.js:*:*

Protect Your Infrastructure against CVE-2026-8161: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-9632 – A flaw has been found in UTT HiPER 1250GW up to 3.2.7-210907-180535. Affected by this issue is the function strcpy of the file /goform/formGroupCon...
  • CVE-2026-9631 – A vulnerability was detected in UTT HiPER 1250GW up to 3.2.7-210907-180535. Affected by this vulnerability is the function strcpy of the file /gofo...
  • CVE-2026-9628 – A weakness has been identified in UTT HiPER 1200GW up to 2.5.3-170306. Affected is an unknown function of the file /goform/formPptpClientConfig of ...
  • CVE-2026-9627 – A security flaw has been discovered in UTT HiPER 1200GW up to 2.5.3-170306. This impacts the function strcpy of the file /goform/setSysAdm of the c...
  • CVE-2026-9609 – A vulnerability was identified in QianFox FoxCMS up to 1.2.6. This affects the function Edit of the file Admin.php. The manipulation leads to weak ...