CVSS 3.1
9.1 criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:HCVE-2026-46350 dcmjs-org dcmjs: Improper Input Validation
Critical (9.1) in dcmjs-org dcmjs. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in dcmjs 0.52.0.
On this page
dcmjs is a JavaScript implementation of DICOM manipulation. Prior to 0.52.0, the DecimalString and IntegerString implementations in src/ValueRepresentation.js sanitize text with a permissive regular expression and pass the result to JavaScript's Number constructor without validating finiteness or the DICOM value-representation rules. Scientific notation overflow in a DS or IS field can produce positive or negative Infinity, while stripping alphabetic characters from signed infinity text can leave a sign-only string that converts to NaN. IntegerString also accepts exponent notation and values outside the DICOM signed 32-bit IS range. Applications that trust these parsed values can propagate invalid numbers into spatial geometry, display windowing, dose scaling, frame counts, rescaling, or volume reconstruction, causing incorrect calculations or disrupted processing. This issue is fixed in version 0.52.0.
Severity
- EPSS
- 0.6% (unchanged from 0.6% a week ago) estimated probability of exploitation activity in the next 30 days; 49th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-11-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- OWASP Top 10
- A05:2025 Injection
- Published
- Modified
- NVD analysis
- Deferred: the NVD does not plan to analyze it
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-46350 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-46350?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-46350?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-46350 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-46350)
HTML:
<a href="https://cve.bz/cve/CVE-2026-46350"><img src="https://cve.bz/cve/badge/CVE-2026-46350.svg" alt="CVE-2026-46350"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| dcmjs-org dcmjs | < 0.52.0 |
Fix and patched versions
dcmjs(npm): fixed in 0.52.0
Packages (OSV)
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-px68-xx5g-48q5 | npm | dcmjs | <0.52.0 | 0.52.0 |
Attack patterns (CAPEC)
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).
History
- The NVD deferred its analysis
Changes since this site first stored the record. The same for every record: /api/public/changes.