VulnerabilityPublished 7 Jan 2026Updated 23 Feb 2026

CVE-2024-14020: carboneio carbone · Improperly Controlled Modification of Object Prototype Attributes

Affects carboneio carboneSource CVE Database V5

Not known to be exploited · CVSS 2.3 Low · fixed in 3.5.6 : update carboneio carbone when convenient.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 4.0 base score

2.3Low

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

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

CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X

Attack Vector: Network
Attack Complexity: High
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: High: The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques, for example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful; Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system 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 Vulnerable System.
Vulnerable system 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 to the Vulnerable System.
Vulnerable system 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 Vulnerable System 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 Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 7 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC 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

Affected software

Product	Affected	Fixed in
carboneiocarbone	Affected =fbcd349077ad0e8748be73eab2a82ea92b6f8a7e	Fixed in–

AI-suggested

Organizations should upgrade the carbone library to version 3.5.6 or later, which contains the patch addressing this vulnerability. Additionally, developers should audit their parent NodeJS applications for prototype pollution vulnerabilities or similar security issues that could be leveraged in conjunction with this flaw. Implementing strict input validation and sanitization in the Formatter Handler component and other parts of the application can help prevent prototype pollution attacks. Employing runtime security tools that detect prototype pollution attempts and monitoring application behavior for anomalies related to object prototype manipulation are recommended. Finally, maintaining an up-to-date dependency management process and regularly applying security patches will reduce exposure to this and similar vulnerabilities.

Description

A weakness has been identified in carboneio carbone up to fbcd349077ad0e8748be73eab2a82ea92b6f8a7e. This impacts an unknown function of the file lib/input.js of the component Formatter Handler. Executing a manipulation can lead to improperly controlled modification of object prototype attributes. The attack can be launched remotely. This attack is characterized by high complexity. The exploitability is said to be difficult. Upgrading to version 3.5.6 will fix this issue. This patch is called 04f9feb24bfca23567706392f9ad2c53bbe4134e. You should upgrade the affected component. A successful exploitation can "only occur if the parent NodeJS application has the same security issue".

Impact

The impact of this vulnerability is limited due to its low CVSS score and the high complexity required for exploitation. Successful exploitation could allow an attacker to modify object prototype attributes, potentially leading to unexpected application behavior or security bypasses within the carbone library. However, since the vulnerability's exploitation depends on the parent NodeJS application also having a similar security issue, the overall risk to organizations is reduced. The confidentiality, integrity, and availability impacts are low, meaning sensitive data exposure or system disruption is unlikely. Organizations using carbone for document generation in NodeJS environments might face some risk if their applications are also vulnerable to prototype pollution. Given the niche nature of the library and the complexity of exploitation, widespread impact is expected to be minimal.

Summary

CVE-2024-14020 identifies a prototype pollution vulnerability in the carboneio carbone library, a NodeJS-based document generation tool. The flaw exists in the Formatter Handler component, specifically within the lib/input.js file, where an attacker can manipulate object prototype attributes improperly. Prototype pollution occurs when an attacker modifies the prototype of a base object, potentially influencing all objects inheriting from it, which can lead to unexpected behavior or security issues. However, this vulnerability requires a high level of complexity to exploit remotely, with no user interaction needed and no privileges required beyond low-level privileges. The attack's success also depends on the parent NodeJS application having a similar security flaw, limiting the scope of impact. The vulnerability is fixed in carbone version 3.5.6, which includes a patch identified by commit 04f9feb24bfca23567706392f9ad2c53bbe4134e. The CVSS 4.0 vector indicates network attack vector, high attack complexity, no privileges required, no user interaction, and low impact on confidentiality, integrity, and availability. No known exploits have been reported in the wild, and the vulnerability was published on January 7, 2026.

References

Community reviews

Loading reviews…