CVE-2026-25754VulnerabilityPublished 6 Feb 2026Updated 9 Feb 2026

CVE-2026-25754: adonisjs core · Prototype Pollution

Affects adonisjs coreSource CVE Database V5

Not known to be exploited · CVSS 7.2 High : upgrade to 11.0.0-next.9 or 10.1.3 soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

7.2High

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 11.0.0-next.9, 10.1.3

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

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

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: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
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: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Feb 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 2026-10-26.

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

Upgrade adonisjs core to 11.0.0-next.9 or 10.1.3.

Affected software

Product	Affected	Fixed in
adonisjscore	Affected <10.1.3 <11.0.0-next.9	Fixed in 11.0.0-next.9 10.1.3

AI-suggested

1. Upgrade all AdonisJS core installations to version 10.1.3 or later, or 11.0.0-next.9 or later, as these versions contain the patch for this vulnerability. 2. Conduct a thorough audit of multipart form-data handling in custom application code to ensure no unsafe prototype modifications occur. 3. Implement strict input validation and sanitization on all multipart form-data inputs to prevent injection of malicious payloads. 4. Employ runtime application self-protection (RASP) or Web Application Firewalls (WAF) capable of detecting and blocking suspicious prototype pollution attempts. 5. Monitor application logs for unusual prototype manipulation patterns or errors indicative of exploitation attempts. 6. Educate development teams about prototype pollution risks and secure coding practices related to object property handling. 7. Establish a patch management process to promptly apply security updates for third-party frameworks and dependencies. 8. Consider isolating critical services and minimizing exposure of vulnerable endpoints to the public internet where feasible.

Description

AdonisJS is a TypeScript-first web framework. Prior to versions 10.1.3 and 11.0.0-next.9, a prototype pollution vulnerability in AdonisJS multipart form-data parsing may allow a remote attacker to manipulate object prototypes at runtime. This issue has been patched in versions 10.1.3 and 11.0.0-next.9.

Impact

For European organizations, this vulnerability poses a significant risk to web applications built on vulnerable versions of AdonisJS. Exploitation can lead to unauthorized modification of application logic and data, potentially exposing sensitive information or enabling further attacks such as privilege escalation or injection of malicious code. Sectors relying on Node.js frameworks for critical services—such as finance, healthcare, government, and e-commerce—may face data breaches or service integrity issues. The vulnerability’s remote exploitability without authentication increases the attack surface, especially for externally facing applications. Given the interconnected nature of European IT ecosystems, a successful attack could propagate through supply chains or interconnected services. Additionally, regulatory frameworks like GDPR impose strict data protection requirements, so exploitation leading to data leakage could result in legal and financial penalties. The absence of known exploits in the wild provides a window for proactive mitigation, but the high severity score underscores the urgency of patching.

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 14 Feb 2026, 12:12 UTC

WeaknessesCWE-1321

Technical details

References

Community reviews

Related threats