CVE-2026-81928
Last modified
CVE-2026-81928 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. 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. EPSS estimates a 0.48% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| — | — | < 1.57 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-81928?
How severe is CVE-2026-81928?
How do I fix CVE-2026-81928?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-81922Concrete CMS before 9.5.3 did not enforce a per-page authori…2.7
- CVE-2026-81923In Concrete CMS before 9.5.3, the SEO Bulk Update Meta Tags …2.7
- CVE-2026-81924Concrete CMS before 9.5.3 is vulnerable to Cross-Site Reques…6.5
- CVE-2026-81925Concrete CMS before 9.5.3 improperly neutralized a user-supp…6.1
- CVE-2026-81926Concrete CMS 9.4.0 through 9.5.2 did not escape colliding pa…6.1
- CVE-2026-81927Concrete CMS before 9.5.3 contained a stored cross-site scri…5.4
- CVE-2026-81929The Ocean Pro Demos and Ocean eComm Treasure Box plugins for…7.2
- CVE-2026-8193A weakness has been identified in Akaunting 3.1.21. This iss…6.3
- CVE-2026-81930Apache Airflow's Snowflake provider did not validate the con…6.3
- CVE-2026-81931Unrestricted Upload of File with Dangerous Type in the produ…4.8
- CVE-2026-81932IBM Guardium Data Protection 12.0, 12.1, and 12.2 is vulnera…9.8
- CVE-2026-81933IBM Guardium Data Protection 12.2 is vulnerable to a SQL inj…8.8
Are you affected by CVE-2026-81928?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
