CVE-2026-46350

waiting for further signalsZero needs more public information before it can validate it.

GHSA-px68-xx5g-48q5 ↗EUVD-2026-117784 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
dcmjs-org dcmjs < 0.52.0
fixed in 0.52.0
CWE-20 Improper Input Validation
ETK-2026-3664Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:npm/dcmjs
1h 58msince last run
7mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+0h35m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

dcmjs versions before 0.52.0 can accept malformed DICOM Decimal String and Integer String values as invalid or out-of-range numbers. An attacker who can supply DICOM data to an application that relies on these parsed values may cause incorrect calculations or disrupt image-processing workflows.

mitigation

Upgrade dcmjs to version 0.52.0 or later. Until upgraded, reject malformed and out-of-range DS and IS values before they reach application calculations.

fixed in 0.52.0

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
7m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-05 20:18Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-05 20:18Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-46350

{
  "etk_id": "ETK-2026-3664",
  "cve_id": "CVE-2026-46350",
  "display_id": "CVE-2026-46350",
  "ghsa_id": "GHSA-px68-xx5g-48q5",
  "euvd_id": "EUVD-2026-117784",
  "status": "published",
  "anchor_state": "anchored",
  "title": "DICOM numeric input validation bypass in dcmjs",
  "summary": "dcmjs versions before 0.52.0 can accept malformed DICOM Decimal String and Integer String values as invalid or out-of-range numbers. An attacker who can supply DICOM data to an application that relies on these parsed values may cause incorrect calculations or disrupt image-processing workflows.",
  "mitigation": "Upgrade dcmjs to version 0.52.0 or later. Until upgraded, reject malformed and out-of-range DS and IS values before they reach application calculations.",
  "vendor": "dcmjs-org",
  "product": "dcmjs",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 0.52.0"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "0.52.0"
      ],
      "package_name": "dcmjs",
      "purl": "pkg:npm/dcmjs"
    }
  ],
  "cwes": [
    20
  ],
  "cvss_score": 9.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 6.949503133333334,
  "t0_at": "2026-11-05T20:18:20.099000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-05T20:18:20.099000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-05T20:18:20.099000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-46350"
    }
  }
}

published 2026-11-05 20:46Z
last change 2026-11-05 21:43Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.