Cyber Resilience

CVE-2026-48068

Published
14 July 2026
Modified
21 July 2026
CVSS Score v3.1 7.5
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:H
EPSS Score 0.0062 46th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2026-48068 is a high-severity Uncaught Exception (CWE-248) vulnerability. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Application or System Exploitation (T1499.004); ranked at the 46th 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 SI-10 (Information Input Validation) and SI-11 (Error Handling) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A10:2025 Mishandling of Exceptional Conditions

EU & UK References

Vulnerability Data

@grpc/grps-js implements the core functionality of gRPC purely in JavaScript, without a C++ addon. Prior to 1.9.16, 1.10.12, 1.11.4, 1.12.7, 1.13.5, and 1.14.4, an invalid incoming HTTP/2 stream initiation can cause a server process created using @grpc/grpc-js to crash. This…

more

issue is fixed in versions 1.9.16, 1.10.12, 1.11.4, 1.12.7, 1.13.5, and 1.14.4.

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?

Invalid HTTP/2 input triggers uncaught exception crash in gRPC server, directly enabling remote application DoS via exploitation.

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-48038Shared 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

Control response

Prevent
Stop it (NIST 800-53)
  • SI-10 Information Input Validation
  • SI-11 Error Handling
  • SC-5 Denial-of-service Protection
Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match
prevent

Validates incoming HTTP/2 streams to reject malformed initiation frames before they trigger an uncaught exception.

SI-11 Error Handling good match
prevent

Ensures uncaught exceptions from invalid gRPC streams are handled gracefully instead of crashing the server process.

SC-5 Denial-of-service Protection partial match
prevent

Limits the impact of resource-exhaustion DoS attempts that exploit the HTTP/2 stream-handling flaw.

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