CVE-2026-5947 Vulnerability Analysis & Exploit Details

CVE-2026-5947
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2026-5947 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-5947 Details

Status: Modified

Last updated: 🕐 24 Aug 2026, 13:19 UTC
Originally published on: 🕐 20 May 2026, 13:16 UTC

Time between publication and last update: 96 days

CVSS Release: version 3

CVSS3 Source

security-officer@isc.org

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CVE-2026-5947 Vulnerability Summary

CVE-2026-5947: Undefined behavior may result due to a race condition leading to a use-after-free violation. If BIND receives an incoming DNS message signed with SIG(0), it begins work to validate that signature. If, during that validation, the "recursive-clients" limit is reached (as would occur during a query flood), and that same DNS message is discarded per the limit, there is a brief window of time while the SIG(0) validation may attempt to read the now-discarded DNS message. This issue affects BIND 9 versions 9.20.0 through 9.20.22, 9.21.0 through 9.21.21, and 9.20.9-S1 through 9.20.22-S1. BIND 9 versions 9.18.28 through 9.18.49 and 9.18.28-S1 through 9.18.49-S1 are NOT affected.

Assessing the Risk of CVE-2026-5947

Access Complexity Graph

The exploitability of CVE-2026-5947 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-5947

With low attack complexity and no required privileges, CVE-2026-5947 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-5947, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-5947, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2026-5947 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2026-5947 poses no threat to data integrity.
  • Availability: High
    CVE-2026-5947 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2026-5947 References

External References

CWE Common Weakness Enumeration

CWE-367

CAPEC Common Attack Pattern Enumeration and Classification

  • Leveraging Race Conditions via Symbolic Links CAPEC-27 This attack leverages the use of symbolic links (Symlinks) in order to write to sensitive files. An attacker can create a Symlink link to a target file not otherwise accessible to them. When the privileged program tries to create a temporary file with the same name as the Symlink link, it will actually write to the target file pointed to by the attackers' Symlink link. If the attacker can insert malicious content in the temporary file they will be writing to the sensitive file by using the Symlink. The race occurs because the system checks if the temporary file exists, then creates the file. The attacker would typically create the Symlink during the interval between the check and the creation of the temporary file.
  • Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions CAPEC-29 This attack targets a race condition occurring between the time of check (state) for a resource and the time of use of a resource. A typical example is file access. The adversary can leverage a file access race condition by "running the race", meaning that they would modify the resource between the first time the target program accesses the file and the time the target program uses the file. During that period of time, the adversary could replace or modify the file, causing the application to behave unexpectedly.

Vulnerable Configurations

  • cpe:2.3:a:isc:bind:9.20.0:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.20.0:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.20.1:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.20.1:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.20.2:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.20.2:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.20.3:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.20.3:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.20.4:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.20.4:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.20.5:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.20.5:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.20.6:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.20.6:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.20.7:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.20.7:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.20.8:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.20.8:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.20.9:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.20.9:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.20.10:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.20.10:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.20.11:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.20.11:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.20.12:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.20.12:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.20.13:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.20.13:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.20.15:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.20.15:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.20.16:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.20.16:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.20.17:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.20.17:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.20.18:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.20.18:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.20.19:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.20.19:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.20.20:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.20.20:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.20.21:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.20.21:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.20.22:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.20.22:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.21.0:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.21.0:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.21.1:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.21.1:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.21.2:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.21.2:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.21.3:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.21.3:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.21.4:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.21.4:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.21.5:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.21.5:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.21.6:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.21.6:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.21.7:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.21.7:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.21.8:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.21.8:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.21.9:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.21.9:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.21.10:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.21.10:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.21.11:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.21.11:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.21.12:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.21.12:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.21.14:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.21.14:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.21.15:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.21.15:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.21.16:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.21.16:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.21.17:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.21.17:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.21.18:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.21.18:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.21.19:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.21.19:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.21.20:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.21.20:*:*:*:-:*:*:*
  • cpe:2.3:a:isc:bind:9.21.21:*:*:*:-:*:*:*
    cpe:2.3:a:isc:bind:9.21.21:*:*:*:-:*:*:*

Protect Your Infrastructure against CVE-2026-5947: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-107121 – A flaw was found in the SMTP email configuration handling of the keycloak-services component. When the STARTTLS option is enabled, Keycloak fails t...
  • CVE-2026-97354 – The PowerPress Podcasting plugin by Blubrry WordPress plugin before 11.17.11 does not validate the destination of redirects when fetching a user-su...
  • CVE-2026-97331 – The User Private Files WordPress plugin before 2.1.9 does not validate that a supplied user belongs to the document being operated on before retur...
  • CVE-2026-97188 – The String locator WordPress plugin before 2.6.8 does not restrict the classes allowed when deserializing the content of a database row saved throu...
  • CVE-2026-96530 – The Optimole WordPress plugin before 4.2.15 does not perform a capability check before exposing its stored image-optimization account data in a da...