Security Resilience

CVE-2025-70023

Memory Safety

Published
14 April 2026
Modified
17 April 2026
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0045 38th percentile
Risk Priority 71 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-70023 is a critical-severity Type Confusion (CWE-843) vulnerability. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Client Execution (T1203); ranked at the 38th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-70023 is a vulnerability classified under CWE-843 (Access of Resource Using Incompatible Type) affecting transloadit uppy version 0.25.6. Uppy is an open-source JavaScript library for file uploading and processing. The issue was published on 2026-04-14T18:16:41.677 and carries a CVSS v3.1 base score of 9.8, indicating critical severity due to its network accessibility, low attack complexity, lack of required privileges or user interaction, and high impacts on confidentiality, integrity, and availability.

The vulnerability can be exploited by any remote attacker with network access to an affected Uppy instance, requiring no authentication, privileges, or user interaction. Successful exploitation allows the attacker to achieve high-level compromise, including unauthorized access to sensitive data (C:H), modification of system resources (I:H), and disruption of service availability (A:H), all within the unchanged security scope (S:U).

Mitigation details are available in referenced advisories, including a GitHub Gist at https://gist.github.com/zcxlighthouse/27926a85371ac5d2291f44903254753e, the Transloadit GitHub organization at https://github.com/transloadi, and the official Uppy repository at https://github.com/transloadit/uppy. Security practitioners should consult these sources for patch information, upgrade guidance, or workarounds specific to version 0.25.6.

EU & UK References

Vulnerability Data

An issue pertaining to CWE-843: Access of Resource Using Incompatible Type was discovered in transloadit uppy v0.25.6.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1204.002 Malicious File Execution
An adversary may rely upon a user opening a malicious file in order to gain execution.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-40446Shared CWE-843
CVE-2025-43355Shared CWE-843
CVE-2023-1235Shared CWE-843
CVE-2026-58283Shared CWE-843
CVE-2025-32948Shared CWE-843
CVE-2026-102869Shared CWE-843
CVE-2026-57975Shared CWE-843
CVE-2017-11292Shared CWE-843
CVE-2016-7201Shared CWE-843
CVE-2024-2887Shared CWE-843

Affected Assets

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.5.2
  • V15.3.5

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation (including fuzzing and type-aware analysis) directly finds type-confusion flaws before deployment.

Engineering principles can require use of type-safe languages, static typing, and runtime type checks that structurally avoid allocating one type and accessing another.

Memory-protection controls limit the blast radius when a type-confusion access occurs but do not stop the flaw itself.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly prevent type-confusion flaws via safe typing, static analysis, and code review while the control itself addresses many additional weaknesses.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development can detect type-confusion vulnerabilities through fuzzing and static analysis.

prevents

Secure coding standards directly forbid unsafe type casts and require static-analysis checks for type confusion.

References