CVE-2026-81928

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-02. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — Patch released this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

Net::DNS versions before 1.57 for Perl allow memory exhaustion via unbounded recursion in sig_data when re-encoding a message with a misplaced TSIG record.

sig_data signs a message by re-encoding it, and removes TSIG records only from the additional section. A TSIG decoded into the answer or authority section survives that step and is signed again, so encoding re-enters sig_data with no termination condition. Decoding does not reject such a message: a TSIG that is not the last record on the wire raises "misplaced or corrupt TSIG", but the error is caught, reported as a warning, and the record is left in the packet. RFC 8945 section 5.2 requires the message to be dropped.

The recursion is reached only when the decoded TSIG carries an empty MAC, since a MAC recovered from the wire short-circuits the signing step. It is reached only from code that re-encodes a message it decoded, such as a forwarder or a proxy. A decoded message that is never re-encoded is unaffected. Message direction does not matter: a query reaches the same path as a response.

Each cycle re-encodes the whole message, so fewer than 100 bytes on the wire exhaust available memory and terminate the process.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
41%
KEV
Not listed

Published

September 1, 2026

Last Modified

September 3, 2026

Advisory Details (4)

Auto-updated Sep 2, 2026
No patch confirmed yet.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatperl-Net-DNS-0:1.15-2.el8_102026-09-18redhat
redhatperl-Net-DNS-0:1.29-6.el9_8.12026-09-18redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libnet-dns-perl1.36-1 ... 1.57-1 (20 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libnet-dns-perl1.50-1 ... 1.57-1 (7 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libnet-dns-perl1.50-1, 1.53-1, 1.54-1, 1.55-1, 1.56-11.57-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 27× in last 7d / 72× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 01:36 UTCEG score recompute
  2. 2026-09-19 01:36 UTCVendor advisory
  3. 2026-09-19 01:36 UTCGHSA enrichment
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 12:55 UTCVendor advisory
  6. 2026-09-18 12:55 UTCGHSA enrichment
  7. 2026-09-18 00:14 UTCEG score recompute
  8. 2026-09-18 00:14 UTCGHSA enrichment
  9. 2026-09-17 11:32 UTCGHSA enrichment
  10. 2026-09-16 22:51 UTCEG score recompute
  11. 2026-09-16 22:50 UTCGHSA enrichment
  12. 2026-09-16 14:08 UTCEPSS rescore
  13. 2026-09-16 10:09 UTCEG score recompute
  14. 2026-09-16 10:09 UTCGHSA enrichment
  15. 2026-09-16 05:15 UTCEPSS rescore
  16. 2026-09-15 21:27 UTCGHSA enrichment
  17. 2026-09-15 08:46 UTCEG score recompute
  18. 2026-09-15 08:46 UTCGHSA enrichment
  19. 2026-09-15 03:12 UTCEPSS rescore
  20. 2026-09-15 03:12 UTCEPSS rescore
  21. 2026-09-14 20:02 UTCGHSA enrichment
  22. 2026-09-14 07:21 UTCGHSA enrichment
  23. 2026-09-13 18:39 UTCEG score recompute
  24. 2026-09-13 18:39 UTCGHSA enrichment
  25. 2026-09-13 05:57 UTCGHSA enrichment
Show 47 more
  1. 2026-09-12 17:16 UTCEG score recompute
  2. 2026-09-12 17:16 UTCGHSA enrichment
  3. 2026-09-12 04:34 UTCGHSA enrichment
  4. 2026-09-11 15:52 UTCEG score recompute
  5. 2026-09-11 15:52 UTCGHSA enrichment
  6. 2026-09-11 14:53 UTCEPSS rescore
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-11 03:11 UTCGHSA enrichment
  9. 2026-09-10 14:29 UTCEG score recompute
  10. 2026-09-10 14:29 UTCGHSA enrichment
  11. 2026-09-10 01:47 UTCGHSA enrichment
  12. 2026-09-09 13:05 UTCGHSA enrichment
  13. 2026-09-09 00:23 UTCEG score recompute
  14. 2026-09-09 00:23 UTCGHSA enrichment
  15. 2026-09-08 22:01 UTCEPSS rescore
  16. 2026-09-08 11:20 UTCGHSA enrichment
  17. 2026-09-07 22:38 UTCEG score recompute
  18. 2026-09-07 22:38 UTCGHSA enrichment
  19. 2026-09-07 09:57 UTCGHSA enrichment
  20. 2026-09-06 21:09 UTCEG score recompute
  21. 2026-09-06 21:09 UTCGHSA enrichment
  22. 2026-09-06 13:48 UTCEPSS rescore
  23. 2026-09-06 08:26 UTCGHSA enrichment
  24. 2026-09-05 19:44 UTCEG score recompute
  25. 2026-09-05 19:44 UTCGHSA enrichment
  26. 2026-09-05 15:31 UTCEPSS rescore
  27. 2026-09-05 07:03 UTCGHSA enrichment
  28. 2026-09-04 18:21 UTCEG score recompute
  29. 2026-09-04 18:21 UTCGHSA enrichment
  30. 2026-09-04 05:40 UTCEG score recompute
  31. 2026-09-04 05:39 UTCGHSA enrichment
  32. 2026-09-04 05:07 UTCEPSS rescore
  33. 2026-09-03 16:55 UTCGHSA enrichment
  34. 2026-09-03 09:03 UTCEG score recompute
  35. 2026-09-03 09:03 UTCGHSA enrichment
  36. 2026-09-02 20:22 UTCGHSA enrichment
  37. 2026-09-02 19:30 UTCEG score recompute 7.50
  38. 2026-09-02 19:30 UTCGHSA enrichment
  39. 2026-09-02 19:30 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  40. 2026-09-02 14:12 UTCEPSS rescore
  41. 2026-09-02 11:26 UTCGHSA enrichment
  42. 2026-09-02 11:21 UTCNVD update
  43. 2026-09-02 10:26 UTCGHSA enrichment
  44. 2026-09-02 10:23 UTCMITRE cvelistV5
  45. 2026-09-02 00:22 UTCNVD update
  46. 2026-09-01 23:26 UTCEG score recompute
  47. 2026-09-01 23:25 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-81928?
CVE-2026-81928 is a high vulnerability published on September 1, 2026. Net::DNS versions before 1.57 for Perl allow memory exhaustion via unbounded recursion in sig_data when re-encoding a message with a misplaced TSIG record. sigdata signs a message by re-encoding it, and removes TSIG records only from the additional section. A TSIG decoded into the answer or…
When was CVE-2026-81928 disclosed?
CVE-2026-81928 was first published in the National Vulnerability Database on September 1, 2026, with the most recent update on September 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-81928 actively exploited?
CVE-2026-81928 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 59.2% of all scored CVEs.
What is the CVSS score of CVE-2026-81928?
CVE-2026-81928 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-81928?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-81928, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-81928

Explore →

Is Your Infrastructure Affected by CVE-2026-81928?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.