LiveActive security incident?Get immediate response
CVE Record

CVE-2019-6446: An issue was discovered in NumPy before 1.16.3.

An issue was discovered in NumPy before 1.16.3. It uses the pickle Python module unsafely, which allows remote attackers to execute arbitrary code via a crafted serialized object, as demonstrated by a numpy.load call. NOTE: third parties dispute this issue because it is a behavior that might have legitimate applications in (for example) loading serialized Python object arrays from trusted and authenticated sources.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

Older NumPy versions loaded Python pickle data through numpy.load in a way that could run attacker-controlled code if an application opened a malicious serialized object. Business risk depends on whether systems process NumPy files from untrusted users, partners, pipelines, or storage. The CVE is disputed because this behavior can be legitimate for trusted object arrays. Exposure is most likely in Python services, notebooks, batch jobs, ML pipelines, or data-processing tools using NumPy before 1.16.3 and loading serialized arrays from untrusted or weakly authenticated sources. Prioritize remediation for internet-facing upload features, shared data platforms, and ML pipelines consuming third-party files. Lower urgency may be reasonable for isolated systems that only load trusted internal artifacts, but the trust boundary should be verified rather than assumed. Mitigation focus: Upgrade NumPy to 1.16.3 or later where vendor guidance supports it.; Do not load NumPy pickle/object data from untrusted sources.; Require authentication and provenance checks for serialized data inputs..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-6446 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
10Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.