Which products and versions are affected by CVE-2026-94300?

Affected: Bind (Isc); bind9 (debian); bind-main (redhat), among others. The full list is in the CVE brief.

Is CVE-2026-94300 being exploited in the wild?

It is not listed in any known-exploited vulnerabilities catalog.

Is CVE-2026-94300 in the CISA KEV catalog?

No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.

Is there a public exploit for CVE-2026-94300?

No public exploit code is known.

Is there a fix for CVE-2026-94300?

Fixed versions are available, including bind-main 9.20.30-0.1.hum1, bind9 1:9.20.30-1~deb13u1, Bind 9.18.50.

How urgently should CVE-2026-94300 be patched?

Brandefense priority: patch in the next maintenance window, because of its high severity, although no exploitation is known.

Request A Demo

High

CVE-2026-94300Bind Vulnerability

Replaying GSS-TSIG signed UDP messages can result in memory corruption in "named".

Published Oct 21, 2026 · Updated Oct 22, 2026 · Also known as EUVD-2026-107254, GHSA-3g58-6x5w-h3fm

The full analysis for this CVE is not ready yet, so this page shows the scores and scope from the public record. How CVEs are selected

Key Facts

Patch in the next maintenance window

CVE-2026-94300 is a high-severity vulnerability (CVSS 8.1 v3.1) affecting Bind (Isc), bind9 (debian), bind-main (redhat) and 1 more product.
It is not listed in any known-exploited vulnerabilities catalog. No public exploit code is known.
EPSS estimates a 0.7% probability of exploitation in the next 30 days.
Fixed versions are available, including bind-main 9.20.30-0.1.hum1, bind9 1:9.20.30-1~deb13u1, Bind 9.18.50.
Brandefense priority: patch in the next maintenance window, because of its high severity, although no exploitation is known.

Scores

CVSS v3.1

8.1

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

EPSS (30-day exploit likelihood)

0.7%

Higher than 53.8% of all scored CVEs

Exploit maturity

None known

ATLAS score

n/a

Outside the curated set

Description

Replaying GSS-TSIG signed UDP messages can result in memory corruption in "named". An attacker who can capture a previously signed UDP message can replay it while the negotiated TSIG key is still valid.

By also sending crafted queries to a zone the attacker controls, the attacker may potentially achieve remote code execution. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.29, 9.21.0 through 9.21.26, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.29-S1.

Affected Products

8 affected entries in total

Product	Affected versions	Fixed in
BindIsc	See advisory	9.18.50
bind9debian	See advisory	1:9.20.30-1~deb13u1
bind-mainredhat	See advisory	9.20.30-0.1.hum1
BIND 9	>= 9.11.0	n/a

Patched Releases

bind-main

9.20.30-0.1.hum1

bind9

1:9.20.30-1~deb13u1

Bind

9.18.50

Timeline

Publicly disclosed
Oct 21, 2026
Last updated
Oct 22, 2026

Weakness Type

CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
CWE-366 Race Condition within a Thread
CWE-415 Double Free

References

FAQ

Common Questions.

Replaying GSS-TSIG signed UDP messages can result in memory corruption in "named".
Affected: Bind (Isc); bind9 (debian); bind-main (redhat), among others. The full list is in the CVE brief.
It is not listed in any known-exploited vulnerabilities catalog.
No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
No public exploit code is known.
Fixed versions are available, including bind-main 9.20.30-0.1.hum1, bind9 1:9.20.30-1~deb13u1, Bind 9.18.50.
Brandefense priority: patch in the next maintenance window, because of its high severity, although no exploitation is known.

Is CVE-2026-94300 On Your Attack Surface?

Brandefense matches it against the products discovered on your perimeter and opens a finding the day a CVE like this is listed.