Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA isc

CVE-2026-94300: Concurrent GSS-TSIG messages corrupt memory

Noroxi assessment

Priority: Monitor (action score 32/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.95% (FIRST EPSS); higher than 61.3% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: azl3 bind 9.20.26-1 on Azure Linux 3.0 Release Notes.

Low priority for now. Upgrade to azl3 bind 9.20.26-1 on Azure Linux 3.0 Release Notes or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 8.1 · v3.1—Proof of concept Fix available
Published
Oct 21, 2026
Updated
Oct 26, 2026
EPSS
0.9% · 61th percentile

Report tools

JSON

Action score

32

Monitor

Low priority for now.

CVSS
32 / 40 · 8.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.9%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · isc
8.1
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-94300

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for isc records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (isc). Independent of NVD's CPE analysis and usually ahead of it.

  • ISC BIND 9

    • 9.11.0 and later · up to and including 9.18.50affected
    • 9.20.0 and later · up to and including 9.20.29affected
    • 9.21.0 and later · up to and including 9.21.26affected
    • 9.11.3-S1 and later · up to and including 9.18.50-S1affected
    • 9.20.9-S1 and later · up to and including 9.20.29-S1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10bindbefore 32:9.18.33-15.el10_2.1432:9.18.33-15.el10_2.14
AlmaLinux:10bind-chrootbefore 32:9.18.33-15.el10_2.1432:9.18.33-15.el10_2.14
AlmaLinux:10bind-develbefore 32:9.18.33-15.el10_2.1432:9.18.33-15.el10_2.14
AlmaLinux:10bind-dnssec-utilsbefore 32:9.18.33-15.el10_2.1432:9.18.33-15.el10_2.14
AlmaLinux:10bind-docbefore 32:9.18.33-15.el10_2.1432:9.18.33-15.el10_2.14
AlmaLinux:10bind-libsbefore 32:9.18.33-15.el10_2.1432:9.18.33-15.el10_2.14
AlmaLinux:10bind-licensebefore 32:9.18.33-15.el10_2.1432:9.18.33-15.el10_2.14
AlmaLinux:10bind-utilsbefore 32:9.18.33-15.el10_2.1432:9.18.33-15.el10_2.14
AlmaLinux:9bind9.18before 32:9.18.29-14.el9_8.1232:9.18.29-14.el9_8.12
AlmaLinux:9bind9.18-chrootbefore 32:9.18.29-14.el9_8.1232:9.18.29-14.el9_8.12
AlmaLinux:9bind9.18-develbefore 32:9.18.29-14.el9_8.1232:9.18.29-14.el9_8.12
AlmaLinux:9bind9.18-dnssec-utilsbefore 32:9.18.29-14.el9_8.1232:9.18.29-14.el9_8.12
AlmaLinux:9bind9.18-docbefore 32:9.18.29-14.el9_8.1232:9.18.29-14.el9_8.12
AlmaLinux:9bind9.18-libsbefore 32:9.18.29-14.el9_8.1232:9.18.29-14.el9_8.12
AlmaLinux:9bind9.18-utilsbefore 32:9.18.29-14.el9_8.1232:9.18.29-14.el9_8.12
Alpine:v3.22bindbefore 9.20.30-r09.20.30-r0
Debian:12bind9from 0—
Debian:13bind9before 1:9.20.30-1~deb13u11:9.20.30-1~deb13u1
Debian:14bind9before 1:9.20.30-11:9.20.30-1
openSUSE:Tumbleweedbindbefore 9.20.30-1.19.20.30-1.1
Rocky Linux:10bindbefore 2:9.18.33-15.el10_2.142:9.18.33-15.el10_2.14

Same product

isc: all records

Other highest-scoring records for the same primary product.

  • CVE-2025-40775DNS message with invalid TSIG causes an assertion failure
    35Monitor
  • CVE-2024-12705DNS-over-HTTPS implementation suffers from multiple issues under heavy query load
    35Monitor
  • CVE-2024-11187Many records in the additional section cause CPU exhaustion
    35Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2026-80274Sep 16, 2026 · Validating resolver can abort while caching a mismatched NOQNAME proof
    30Monitor
  • ← EarlierCVE-2026-19630Oct 21, 2026 · Amplified resource exhaustion in inbound message processing
    30Monitor
  • Later →CVE-2026-96888Oct 21, 2026 · Named may terminate unexpectedly when a redirect zone is used with strict QNAME minimization
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
azl3 bind 9.20.26-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
almalinux:bind32:9.18.33-15.el10_2.14 · AlmaLinux:10Package registry (OSV)
almalinux:bind-chroot32:9.18.33-15.el10_2.14 · AlmaLinux:10Package registry (OSV)
almalinux:bind-devel32:9.18.33-15.el10_2.14 · AlmaLinux:10Package registry (OSV)
almalinux:bind-dnssec-utils32:9.18.33-15.el10_2.14 · AlmaLinux:10Package registry (OSV)
almalinux:bind-doc32:9.18.33-15.el10_2.14 · AlmaLinux:10Package registry (OSV)
almalinux:bind-libs32:9.18.33-15.el10_2.14 · AlmaLinux:10Package registry (OSV)
almalinux:bind-license32:9.18.33-15.el10_2.14 · AlmaLinux:10Package registry (OSV)
almalinux:bind-utils32:9.18.33-15.el10_2.14 · AlmaLinux:10Package registry (OSV)
almalinux:bind9.1832:9.18.29-14.el9_8.12 · AlmaLinux:9Package registry (OSV)
almalinux:bind9.18-chroot32:9.18.29-14.el9_8.12 · AlmaLinux:9Package registry (OSV)
almalinux:bind9.18-devel32:9.18.29-14.el9_8.12 · AlmaLinux:9Package registry (OSV)
almalinux:bind9.18-dnssec-utils32:9.18.29-14.el9_8.12 · AlmaLinux:9Package registry (OSV)
alpine:bind9.20.30-r0 · Alpine:v3.22Package registry (OSV)
debian:bind91:9.20.30-1~deb13u1 · Debian:13Package registry (OSV)
opensuse:bind9.20.30-1.1 · openSUSE:TumbleweedPackage registry (OSV)
rocky linux:bind2:9.18.33-15.el10_2.14 · Rocky Linux:10Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:02026-10-23

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. Fix recorded+1 d
  3. First PoC+1 d
  4. TodayNov 1, 2026+11 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Exploit maturitynone → poc
  2. Fix✗ → ✓
  3. SSVC exploitation— → none
  4. Exploit maturity— → none

For records you follow, these changes also arrive as notifications. →

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records