Bind, BIND Supported Preview Edition: contain code execution

At a glance

Bind, BIND Supported Preview Edition: remote code execution. This 2026-10-22 case examines 3 version entries and 3 CVEs, documented releases and checks suited to network access, using CERTFR-2026-AVI-1365.

AI illustration: a dark cybersecurity technology space with restrained golden lighting Illustration · fictional scene
In this article

Retrospective for 2026-10-22, compiled on 27 October 2026. The date identifies the day being analysed; source publication and revision dates are recorded below.

What this advisory changes in your environment

The starting point is CERTFR-2026-AVI-1365, published on 2026-10-22. Its scope includes Bind, BIND Supported Preview Edition. Reported consequences are denial of service, remote code execution. These statements apply to the advisory’s scope; they do not assign every consequence to every product or CVE.

This case contains 3 version entries; CVE identifier count: 3. Track remediation by component: a successful overall update does not demonstrate that Bind and BIND Supported Preview Edition each received their respective fix.

Products and versions to examine

Reference
CERTFR-2026-AVI-1365
Source first published
2026-10-22
Latest source revision available for this day
2026-10-22
Named components
Bind, BIND Supported Preview Edition
CVE identifiers
CVE-2026-94300, CVE-2026-96888, CVE-2026-97313
ComponentPublished condition
Bind< 9.21.27
Bind< 9.20.30
BIND Supported Preview Edition< 9.20.30-S1

For Bind, the published condition is “< 9.21.27”. Compare the version actually loaded with that condition within its own release branch. A fix installed on another edition of Bind, BIND Supported Preview Edition does not close this case.

Mechanism and prerequisites

Code execution can give an attacker the permissions of the affected process. Check the service account and reachable network destinations. Component isolation can reduce lateral movement opportunities, but does not replace the fix.

The primary record CVE-2026-94300, published by isc, covers BIND 9. The retained revision is dated 2026-10-22. Its scope is presented separately from the integrations and product groupings in CERTFR-2026-AVI-1365.

The published metric for CVE-2026-94300 is CVSS 3.1, 8.1/10. The vector below describes technical prerequisites; it does not measure attack frequency or the likelihood that your deployment is compromised.

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

Attack vector
network
Prior privileges
none
User interaction
none
Complexity
high
Weakness
CWE-415, CWE-362

Choose the appropriate intervention

  1. Locate Bind instances, running releases and service owners. Record condition < 9.21.27 in the ticket alongside reference CERTFR-2026-AVI-1365.
  2. Compare the installed branch with the vendor’s Bind release notes. Prepare the package for that branch and a dependent-service test, retaining the pre-change state.
  3. After changing Bind, capture the loaded version again and verify the workflow below. Any exception needs an owner, an exposure-reduction measure and an expiry date.

Verify the fix in a real workflow

Validation scenario to adapt for Bind, BIND Supported Preview Edition: For Bind, test an authorised business flow from each zone reaching the service and confirm management restrictions. If a redundant pair exists, verify both nodes and rule persistence after failover during a planned maintenance window. This is a proposed defensive check, not a claim that testing was performed against third-party systems.

Limit of case CERTFR-2026-AVI-1365: this analysis replaces neither vendor prerequisites nor investigation of your logs. Only documented versions are reproduced; no attack date or victim is invented.

Questions specific to this case

Which condition should be checked for Bind?

Advisory CERTFR-2026-AVI-1365 states: Bind — < 9.21.27. Check the edition and running release; do not extend the published boundary to branches absent from the advisory.

Why not use one fix for Bind and BIND Supported Preview Edition?

CERTFR-2026-AVI-1365 distinguishes these components within a scope containing 3 entries. Match each branch to its own update documentation and functional check.

Which prerequisites does record CVE-2026-94300 specify?

For CVE-2026-94300, the published vector is CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. Verify those conditions on BIND 9 before applying them to an integration named in CERTFR-2026-AVI-1365.

Sources and related reading

Practical guide : Software inventory: prepare for end of support

Explore the decision addressed in this case

Complete source advisory inventory

The article table may be an extract. These lists contain every affected-system entry and CVE in the specified advisory revision. They are not an inventory of your assets and do not map every CVE to every product.

Official source · CERTFR-2026-AVI-1365
Advisory revision : · Checked on :

Affected systems · 3

Original French wording is retained to avoid ambiguous translations of version conditions.

  1. Bind versions antérieures à 9.21.27
  2. Bind versions antérieures à 9.20.30
  3. BIND Supported Preview Edition versions antérieures à 9.20.30-S1
CVE identifiers · 3