CyberSecBulletin

Detection of Error Condition Without Action

CWE-390

The product detects a specific error, but takes no actions to handle the error.

We track 10 vulnerabilities of this type. 100% are rated high or critical, and the average CVSS score is 8.4.

How this weakness is prevented

  • Implementation: Properly handle each exception. This is the recommended solution. Ensure that all exceptions are handled in such a way that you can be sure of the state of your system at any given moment.
  • Implementation: If a function returns an error, it is important to either fix the problem and try again, alert the user that an error has happened and let the program continue, or alert the user and close and cleanup the program.
  • Testing: Subject the product to extensive testing to discover some of the possible instances of where/how errors or return values are not handled. Consider testing techniques such as ad hoc, equivalence partitioning, robustness and fault tolerance, mutation, and fuzzing.

Latest Detection of Error Condition Without Action vulnerabilities

  • 7.5 High severity

    firecracker: Detection of Error Condition Without Action

    CVE-2026-122192AWS

    Improper handling of a failed memory remap in Firecracker versions 0.23.0 through 1.16.1 might allow a guest user with root privileges to read or modify Firecracker VMM process memory via balloon or virtio-mem discard requests on microVMs restored from a snaps

  • 7.4 High severity

    django-rest-framework: Detection of Error Condition Without Action

    CVE-2026-114137Encode

    Django REST framework is a toolkit for building Web APIs. From 3.12.0 until 3.18.2, TokenProxy.delete() in rest_framework/authtoken/models.py uses the proxy's user-id pk while the concrete Token token-string primary key identifies rows, so Django issues a dele

  • 9.4 Critical severity

    libdave: Detection of Error Condition Without Action

    CVE-2026-104480Discord

    Discord libdave before 1.2.0 did not reject an MLS Welcome message when the resulting group roster contained an unrecognized participant. An attacker in control of the DAVE signaling path (the voice gateway, or an equivalent position able to add, alter, or wit

  • 7.8 High severity

    util-linux: Detection of Error Condition Without Action

    CVE-2026-76642Util-linux

    util-linux versions through 2.41.5 and 2.42.2 fail to check mount helper exit status before running post-mount hooks, allowing unprivileged users to execute privileged operations on pre-existing filesystems. Attackers can exploit X-mount.idmap or X-mount.owner

  • 9.1 Critical severity

    Apache Tomcat: Detection of Error Condition Without Action

    CVE-2026-53434Apache

    Detection of Error Condition Without Action vulnerability in Apache Tomcat when configuring CRLs for a FFM based connector. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.22, from 10.1.0-M7 through 10.1.55, from 9.0.83 through 9.0.118. Users are

  • 9.8 Critical severity

    Linux: Use of Uninitialized Resource

    CVE-2026-52989Linux

    In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: propagate nvmet_tcp_build_pdu_iovec() errors to its callers Currently, when nvmet_tcp_build_pdu_iovec() detects an out-of-bounds PDU length or offset, it triggers nvmet_tcp_fatal_er

  • 9.8 Critical severity

    Linux: Detection of Error Condition Without Action

    CVE-2026-43493Linux

    In the Linux kernel, the following vulnerability has been resolved: crypto: pcrypt - Fix handling of MAY_BACKLOG requests MAY_BACKLOG requests can return EBUSY. Handle them by checking for that value and filtering out EINPROGRESS notifications.

  • 7.8 High severity

    Alienware Command Center: Detection of Error Condition Without Action

    CVE-2025-46367Dell

    Dell Alienware Command Center 6.x (AWCC), versions prior to 6.10.15.0, contain a Detection of Error Condition Without Action vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Arbitrary Code Exec

  • 7.5 High severity

    envoy: Detection of Error Condition Without Action

    CVE-2024-30255EnvoyproxyEPSS 85%

    Envoy is a cloud-native, open source edge and service proxy. The HTTP/2 protocol stack in Envoy versions prior to 1.29.3, 1.28.2, 1.27.4, and 1.26.8 are vulnerable to CPU exhaustion due to flood of CONTINUATION frames. Envoy's HTTP/2 codec allows the client to

  • 7.5 High severity

    envoy: Detection of Error Condition Without Action

    CVE-2024-27919EnvoyproxyEPSS 83.9%

    Envoy is a cloud-native, open-source edge and service proxy. In versions 1.29.0 and 1.29.1, theEnvoy HTTP/2 protocol stack is vulnerable to the flood of CONTINUATION frames. Envoy's HTTP/2 codec does not reset a request when header map limits have been exceede