Cyber Resilience

CVE-2026-48038

Published
14 July 2026
Modified
15 July 2026
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS Score 0.0030 22th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-48038 is a medium-severity Uncaught Exception (CWE-248) vulnerability. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Application or System Exploitation (T1499.004); ranked at the 22th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

A10:2025 Mishandling of Exceptional Conditions

EU & UK References

Vulnerability Data

joi is a schema description language and data validator for JavaScript. Prior to 17.13.4 and 18.2.1, denial of service is possible via an untrapped exception in services validating user-supplied JSON or object input with recursive link() schemas. When validate() is…

more

called without try/catch in a request handler, deeply nested input can trigger an unhandled RangeError and potentially crash the process; lower-impact paths using validateAsync() or try/catch produce a RangeError instead of a structured ValidationError. This issue is fixed in versions 17.13.4 and 18.2.1.

CWE(s)
CWE-248

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
attack.mitre.org →
Why these techniques?

Uncaught exception in input validation leads directly to process crash, matching Application or System Exploitation for DoS.

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2025-3891Shared CWE-248
CVE-2026-7183Shared CWE-248
CVE-2025-66305Shared CWE-248
CVE-2026-48068Shared CWE-248
CVE-2025-55194Shared CWE-248
CVE-2026-59892Shared CWE-248
CVE-2025-20171Shared CWE-248
CVE-2026-47480Shared CWE-248
CVE-2026-37554Shared CWE-248
CVE-2026-24175Shared CWE-248

Affected Assets

Mitigating Controls

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

SC-24 Fail in Known State
addresses: CWE-248

Prevents abrupt termination from uncaught exceptions by requiring a defined, preserved-state failure mode.

SI-17 Fail-safe Procedures
addresses: CWE-248

Requires pre-defined safe responses for uncaught exceptions so they do not result in undefined or insecure program termination.

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
prevents

Secure SDLC practices explicitly require structured exception handling to prevent uncaught exceptions from reaching production.

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.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing can detect uncaught exceptions before production deployment.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle includes exception-handling standards that reduce uncaught exceptions.

A.8.26 Application security requirements partial match
prevents

Application security requirements typically mandate robust error and exception handling.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles call for centralized, comprehensive exception management.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly require catching and handling exceptions to prevent crashes or leaks.

References