uhop stream-json up to 3.5.x Assembler missing immutable root of trust in hardware
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 0.46 |
Summary
A vulnerability was found in uhop stream-json up to 3.5.x. It has been declared as problematic. This affects an unknown part of the component Assembler. Executing a manipulation can lead to missing immutable root of trust in hardware. This vulnerability is registered as CVE-2026-104183. The attack needs to be launched locally. No exploit is available. It is recommended to upgrade the affected component.
Details
A vulnerability was found in uhop stream-json up to 3.5.x. It has been declared as problematic. This vulnerability affects some unknown processing of the component Assembler. The manipulation with an unknown input leads to a missing immutable root of trust in hardware vulnerability. The CWE definition for the vulnerability is CWE-1326. A missing immutable root of trust in the hardware results in the ability to bypass secure boot or execute untrusted or adversarial boot code. As an impact it is known to affect integrity, and availability. CVE summarizes:
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.
The advisory is available at github.com. This vulnerability was named CVE-2026-104183 since 10/01/2026. The exploitation appears to be easy. Local access is required to approach this attack. The technical details are unknown and an exploit is not available.
Upgrading to version 3.6.0 eliminates this vulnerability.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
Website
- Product: https://github.com/uhop/stream-json/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.7VulDB Meta Temp Score: 4.6
VulDB Base Score: 4.4
VulDB Temp Score: 4.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.1
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Missing immutable root of trust in hardwareCWE: CWE-1326
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: stream-json 3.6.0
Timeline
10/01/2026 Advisory disclosed10/01/2026 CVE reserved
10/01/2026 VulDB entry created
10/01/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-104183 (🔒)
GCVE (CVE): GCVE-0-2026-104183
GCVE (VulDB): GCVE-100-412810
Entry
Created: 10/01/2026 22:32Changes: 10/01/2026 22:32 (64)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.