CyberSecBulletin
CVE-2026-46509NVD status: Deferred

deepobj: Improperly Controlled Modification of Object Prototype Attributes

Published Updated By the CyberSecBulletin desk

CVE-2026-46509 is a high-severity improperly controlled modification of object prototype attributes vulnerability in deepobj from Ranfdev, with a CVSS 3.1 base score of 8.2 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected deepobj versions: < 1.0.3. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.32% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of deepobj you run against the affected versions below, and install the vendor's latest release.
  2. Read the advisory on github.com for workarounds and exact fixed builds.
  3. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
Ranfdevdeepobj< 1.0.3Not stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
NoneNo data is disclosed.
Integrity
HighData or code can be modified at will.
Availability
LowPerformance or availability is reduced.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L. Scored by CNA (github.com).

Official description

deepobj provides get, set, delete deep objects in javascript. Prior to 1.0.3, prototype pollution is possible when property paths contain __proto__/constructor/prototype. The property path must not be exposed as user input. This vulnerability is fixed in 1.0.3.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improperly Controlled Modification of Object Prototype Attributes

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.

How developers prevent this class of flaw

  • By freezing the object prototype first (for example, Object.freeze(Object.prototype)), modification of the prototype becomes impossible.
  • By blocking modifications of attributes that resolve to object prototype, such as proto or prototype, this weakness can be mitigated.
  • When handling untrusted objects, validating using a schema can be used.

More Improperly Controlled Modification of Object Prototype Attributes vulnerabilities (CWE-1321)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Improperly Controlled Modification of Object Prototype Attributes vulnerabilities

Spotted an error? Tell us.