Skip to main content

Threat Intelligence Database

Comprehensive database of the latest cyber threats affecting organizations worldwide. Filter and search to find specific threat intelligence relevant to your organization.

Pro Console Lifetime

Stop chasing alerts. Route them.

Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.

Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)

View Plans & Pricing

API access activates after upgrading in Console -> Billing.

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now

Filter Threats

Narrow down the results by type, severity, or affected countries

Search threats by title, CVE ID, or description. Maximum 100 characters.
Active filters (1):Package: pkg:npm/stream-json

Threat Intelligence

Click on any threat for detailed analysis and mitigation recommendations

stream-json is a micro-library of stream components for processing JSON and JSONC with a minimal memory footprint. Prior to 3.6.0, Assembler materializes object properties with plain assignment, so an input key named __proto__ invokes the inherited setter and causes parsed object prototype replacement instead of creating an own data property. Applications that make authorization or feature decisions from inherited values can therefore consume attacker-controlled properties, and a null prototype can disrupt code that expects Object.prototype methods. The researcher treats parsing untrusted JSON as part of the project contract, while the maintainer states that documented inputs are locally owned dumps, exports, or logs and characterizes the attack vector as local. The global Object.prototype is not polluted. This issue is fixed in version 3.6.0.

Join the discussion

CVE-2026-104182 is an inefficient algorithmic complexity vulnerability in the JSONC parser and verifier components of the stream-json library prior to version 3.6.0. The issue occurs because the parser restarts scanning for comment terminators from the opening slash whenever a block or line comment spans multiple input chunks, causing quadratic CPU usage and potentially stalling the Node.js event loop. This vulnerability affects only JSONC parsing, not plain JSON parsing. The vulnerability is considered local because the JSONC input is typically user-controlled or locally owned configuration data. The issue is fixed in version 3.6.0.

Join the discussion

Showing 1 to 2 of 2 results

Filters:Package: pkg:npm/stream-json
Page 1 of 1
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses