VulnerabilityPublished 26 Feb 2026

CVE-2026-27837: mickhansen dottie.js · Prototype Pollution

Affects mickhansen dottie.jsSource CVE Database V5

Compare

Mentioned vulnerabilities

CVE-2023-26132

Not known to be exploited · CVSS 6.3 Medium : upgrade to 2.0.7 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

6.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.0.7

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade mickhansen dottie.js to 2.0.7.

Affected software

Product	Affected	Fixed in
mickhansendottie.js	Affected >=2.0.4 <2.0.7	Fixed in 2.0.7
npmdottie.js`pkg:npm/dottie.js`Other threats	Affected >=2.0.4 <=2.0.6	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate the risk posed by CVE-2026-27837, organizations should take the following specific actions: 1) Immediately upgrade all instances of dottie.js to version 2.0.7 or later, which contains the complete fix for the prototype pollution vulnerability. 2) Conduct a thorough dependency audit to identify all projects and components using dottie.js, including transitive dependencies, to ensure comprehensive patching. 3) Implement input validation and sanitization on all user-supplied data that may be passed to dottie.set() or dottie.transform() functions to reduce the risk of malicious path injection. 4) Employ runtime application self-protection (RASP) or monitoring tools to detect anomalous prototype modifications or unexpected behavior indicative of exploitation attempts. 5) Review and harden application logic that depends on nested object manipulation to minimize the impact of potential prototype pollution. 6) Educate development teams about secure coding practices related to prototype pollution and the risks of improper object manipulation. 7) Monitor security advisories and threat intelligence feeds for any emerging exploit techniques targeting this vulnerability. These steps go beyond generic patching by emphasizing comprehensive dependency management, input validation, and proactive detection.

Description

Dottie provides nested object access and manipulation in JavaScript. Versions 2.0.4 through 2.0.6 contain an incomplete fix for CVE-2023-26132. The prototype pollution guard introduced in commit `7d3aee1` only validates the first segment of a dot-separated path, allowing an attacker to bypass the protection by placing `__proto__` at any position other than the first. Both `dottie.set()` and `dottie.transform()` are affected. Version 2.0.7 contains an updated fix to address the residual vulnerability.

Impact

The prototype pollution vulnerability in dottie.js can have significant impacts on affected applications and organizations. By manipulating the prototype of JavaScript objects, attackers can alter application logic, bypass security controls, or introduce unexpected behavior leading to data integrity issues. This can result in unauthorized data modification, privilege escalation within the application context, or denial of service through application crashes or resource exhaustion. Since dottie.js is a utility library commonly used in Node.js and frontend JavaScript applications, the scope of impact includes web applications, APIs, and backend services that rely on it for object manipulation. The vulnerability is exploitable remotely and requires user interaction, which may limit automated exploitation but still poses a risk in scenarios where user input is processed without sufficient validation. Organizations using vulnerable versions may face increased risk of targeted attacks, especially if the library is used in security-critical components. Although no known exploits are reported yet, the presence of a partial fix indicates that attackers may develop techniques to exploit this residual flaw. Failure to update to the patched version could lead to compromise of application integrity and availability.

CWE-1321Improperly Controlled Modification of Object Prototype Attributes (Prototype Pollution) (opens in a new tab)
Variant weakness
The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.
Implementation
By freezing the object prototype first (for example, Object.freeze(Object.prototype)), modification of the prototype becomes impossible.
Architecture and Design
By blocking modifications of attributes that resolve to object prototype, such as proto or prototype, this weakness can be mitigated.
Implementation · Input Validation
When handling untrusted objects, validating using a schema can be used.
OWASP Cheat Sheets
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V5.1.2 (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
Exploiting Incorrectly Configured Access Control Security Levels (opens in a new tab)
Manipulating User-Controlled Variables (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Mar 2026, 11:35 UTC

WeaknessesCWE-1321

Technical details

References

Community reviews

Related threats