BlackTreeCVE IntelligenceUnknown · set-value
High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.
Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | node-set-value | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.0.1-3 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian bookwormbookworm · source | node-set-value | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.0.1-3 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian forkyforky · source | node-set-value | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.0.1-3 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Debian sidsid · source | node-set-value | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.0.1-3 | Debian Security Tracker ↗Source updated 6 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | node-set-value | Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| NuGetset-value-nuget | ECOSYSTEM: introduced 0; fixed 2.0.0 | 2.0.0 | OSV record ↗aggregator derived · 14 Jan 2025 |
| npmset-value | SEMVER: introduced 4.0.0; fixed 4.0.1 | 4.0.1 | OSV record ↗aggregator derived · 14 Jan 2025 |
| npmset-value | SEMVER: introduced 0; fixed 2.0.1 | 2.0.1 | OSV record ↗aggregator derived · 14 Jan 2025 |
| npmset-value | SEMVER: introduced 3.0.0; fixed 3.0.3 | 3.0.3 | OSV record ↗aggregator derived · 14 Jan 2025 |
High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.
Patch availableThis affects the package set-value before <2.0.1, >=3.0.0 <4.0.1. A type confusion vulnerability can lead to a bypass of CVE-2019-10747 when the user-provided keys used in the path parameter are arrays.
This affects the package set-value before <2.0.1, >=3.0.0 <4.0.1. A type confusion vulnerability can lead to a bypass of CVE-2019-10747 when the user-provided keys used in the path parameter are arrays.
The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
This affects the package set-value before <2.0.1, >=3.0.0 <4.0.1. A type confusion vulnerability can lead to a bypass of CVE-2019-10747 when the user-provided keys used in the path parameter are arrays.
The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.
CWE-843: Access of Resource Using Incompatible Type ('Type Confusion'). The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:LCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
Operational remediation based on structured source evidence.
Published 12 Sept 2021 · Last source change 16 Sept 2024, 19:20 UTC · CWE-843 · Access of Resource Using Incompatible Type ('Type Confusion')
Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.
No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.