vciy

CVE-2026-32792

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

Packet of death with DNSCrypt

CVE-2026-327924 of 4 sources documented this
15

rank 15 = 0 + 13 + 0 + 2 + 0

rank@v1 · backlog

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.00337  ·  without this subject the record ranks 15

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 5.3, from NVD  ·  without this subject the record ranks 2

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 15

How much of the world it touches

NVD CPE configurations

1 product in the CPE ranges  ·  without this subject the record ranks 13

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 15

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$10,300over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$10,300 = $4.99M incident cost x 0.6121449559255632 exposure x 0.00337 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.00337EPSSNOT IN KEVas of 2026-09-20
Severity4.6 MEDIUMreceipt
Harmunauthenticated · networkreceipt
Exploitationnone in held sources
Defensefix version namedreceipt
Movementscoring model changedreceipt
PLATEAU10Minimal movement since 2026-05-20, 26 days at 0.00, as of 2026-06-15. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Sources disagree here.

Severity score
NLnet Labs4.6 MEDIUMreceipt
NVD5.3 MEDIUMreceipt
Scoring standard
NLnet LabsCVSS v4.0receipt
NVDCVSS v3.1receipt

Both shown, dated. We don't pick winners. disagreement-rules@v1

Running NLnet Labs Unbound? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · no privileges required · no user interaction · low attack complexity · attack requirements presentreceipt
ImpactComplete availability lossreceipt
Scored fromCVSS v4.0 · the CNA's vectorreceipt
Weakness classCWE-166 Improper Handling of Missing Special Element; CWE-125 Out-of-bounds Readreceipt
Published consequencesCWE-166: Availability: DoS: Crash, Exit, or Restart[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed in1.25.1receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, the CNA4.6 MEDIUMreceipt
CVSS, NVD5.3 MEDIUMreceipt
Exploit probability0.00337 · top 73% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byNLnet Labsreceipt
Recorded changes4 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productNLnet Labs Unboundreceipt
Published rangesnlnetlabs unbound >= 1.6.2 < 1.25.1receipt
Fixed in1.25.1receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

NLnet Labs Unbound 1.6.2 up to and including version 1.25.0 has a denial of service vulnerability when compiled with DNSCrypt support ('--enable-dnscrypt'). A bad DNSCrypt query could underflow Unbound's DNSCrypt packet reading procedure that may lead to heap overflow. A malicious actor can exploit the vulnerability with a single bad DNSCrypt query that its decrypted plaintext consists entirely of '0x00' bytes and does not contain the expected '0x80' marker. Unbound would then start reading more bytes than necessary until it finds a non-'0x00' byte. Based on the underlying memory allocator and the memory layout, it could lead to heap overflow while reading followed by a crash. receipt

Read the rest of the CNA's description

Likelihood of a crash is low, since it relies heavily on the underlying memory allocator and the memory layout. If the heap overflow does not happen, Unbound's later packet checks will deny the packet. Unbound 1.25.1 contains a patch with a fix to bound reading in the given buffer space.

NVD's analysis a second authority

severity
5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
weakness
CWE-125; CWE-166
affected versions
nlnetlabs unbound >= 1.6.2 < 1.25.1
also scored by
[email protected] 4.6 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:Green

The CNA scored it 4.6 and NVD 5.3. Both are shown because both were published; we do not pick one.

check it yourself nlnetlabs.nl receipt

Movement the material steps

20 May 20260.00042
15 Jun 20260.00337 · scoring model v2026.06.15
Show all 4 observations
20 May 20260.00042
21 May 20260.00044
26 May 20260.00058
15 Jun 20260.00337

4 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.00337Published2026-05-20Index as of2026-06-15

The record had been public for 26 days when this index was last written.

Published 2026-05-20 receipt · Index as of 2026-06-15 derived

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2026-32792.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.