Skip to content
Noroxi
CVE-2026-33596· NVD / CVE Program· CNA OX

TCP backend stream ID overflow

Noroxi assessment

Priority: Monitor (action score 26/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.39% (FIRST EPSS).
  • Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: PowerDNS DNSdist 1.9.13, 2.0.4.
  • Severity is disputed: the assigning authority (CNA) scores it 3.1, NVD 6.5.

Low priority for now. Upgrade to PowerDNS DNSdist 1.9.13, 2.0.4 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

A client might theoretically be able to cause a mismatch between queries sent to a backend and the received responses by sending a flood of perfectly timed queries that are routed to a TCP-only or DNS over TLS backend.

MediumCVSS 6.5 · v3.1—No exploit Fix available
Published
Apr 22, 2026
Updated
Jun 17, 2026
EPSS
0.3% · 31th percentile

Report tools

JSON

Action score

26

Monitor

Low priority for now.

CVSS
26 / 40 · 6.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
6.5
CNA · OX
3.1
3.4 point gap

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

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
  • No public exploit code on record
  • A fix has been released

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

Follow CVE-2026-33596

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 powerdns 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.

VendorProduct
powerdnsdnsdist

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • powerdns dnsdist1.9.0 and later · before 1.9.13
  • powerdns dnsdist2.0.0 and later · before 2.0.4

Versions reported by the vendor

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

  • PowerDNS DNSdist

    • 1.9.0 and later · before 1.9.13affected · semver
    • 2.0.0 and later · before 2.0.4affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12dnsdistfrom 0—
Debian:13dnsdistbefore 1.9.14-0+deb13u11.9.14-0+deb13u1
Debian:14dnsdistbefore 2.0.4-12.0.4-1
openSUSE:Leap 16.0dnsdistbefore 1.9.13-160000.1.11.9.13-160000.1.1
openSUSE:Tumbleweeddnsdistbefore 2.0.5-1.12.0.5-1.1
SUSE:Linux Enterprise Server 16.0dnsdistbefore 1.9.13-160000.1.11.9.13-160000.1.1

Same product

powerdns: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-33598Out-of-bounds read in cache inspection via Lua
    37Monitor
  • CVE-2017-7557dnsdist version 1.1.0 is vulnerable to a flaw in authentication mechanism for REST API potentially allowing CSRF attack.
    35Monitor
  • CVE-2026-33602Off-by-one access when processing crafted UDP responses
    32Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2026-33594Apr 22, 2026 · Outgoing DoH excessive memory allocation
    30Monitor
  • ← EarlierCVE-2026-33595Apr 22, 2026 · DoQ/DoH3 excessive memory allocation
    30Monitor
  • Later →CVE-2026-33597Apr 22, 2026 · PRSD detection denial of service
    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
PowerDNS DNSdist1.9.13Vendor (CNA)
PowerDNS DNSdist2.0.4Vendor (CNA)
debian:dnsdist1.9.14-0+deb13u1 · Debian:13Package registry (OSV)
opensuse:dnsdist2.0.5-1.1 · openSUSE:TumbleweedPackage registry (OSV)
suse:dnsdist1.9.13-160000.1.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

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.

No dated events beyond publication.

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

  • Someone on the same network segment can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Adjacent
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-190 · Integer Overflow or Wraparound

CVSS vector

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

nvd-primary

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. Fix✗ → ✓

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

References

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

All records