LiveActive security incident?Get immediate response
CVE Record

CVE-2026-46509: deepobj: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')

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.

HighCVSS 8.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-46509 affects the JavaScript package deepobj before 1.0.3. If an application lets untrusted users control deep property paths, an attacker could alter JavaScript object prototypes, affecting data integrity and potentially availability. The vendor states version 1.0.3 fixes the issue.

Executive priority

Treat as high priority for JavaScript services using deepobj. Prioritize systems that accept user-controlled field paths, JSON structures, configuration keys, or API parameters that reach deep object operations.

Technical view

deepobj before 1.0.3 allows prototype pollution when property paths include __proto__, constructor, or prototype. The CVSS 3.1 score is 8.2, with network attack vector, no privileges, no user interaction, high integrity impact, and low availability impact.

Likely exposure

Exposure is limited to applications using ranfdev deepobj versions before 1.0.3, especially where property paths can be influenced by users or external input. The source bundle does not identify downstream applications or platforms.

Exploitation context

No active exploitation is cited, and KEV status is false. The advisory warns that property paths must not be exposed as user input. Evidence in the bundle supports risk, but not exploitation in the wild.

Researcher notes

The core condition is user influence over path segments containing __proto__, constructor, or prototype. The provided sources do not include proof-of-concept details, exploit telemetry, or broader ecosystem impact. Keep analysis scoped to deepobj before 1.0.3.

Mitigation direction

  • Upgrade deepobj to version 1.0.3 or later.
  • Do not expose deepobj property paths to untrusted user input.
  • Audit dependency manifests and lockfiles for deepobj before 1.0.3.
  • Check vendor guidance for any additional hardening recommendations.

Validation and detection

  • Confirm installed deepobj versions across direct and transitive dependencies.
  • Review code paths passing external input into deepobj get, set, or delete operations.
  • Verify the dependency lockfile resolves deepobj to 1.0.3 or later.
  • Run regression tests covering object mutation and input handling paths.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-1321: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-46509 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.2 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L3.94.2GitHub_M

Vulnerability scoring details

Base CVSS 3.1 score

8.2High
CVSS 3.1 vector shape for CVE-2026-46509Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ranfdevdeepobj< 1.0.3Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-1321 · source CWE mapping

Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')

Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.