RUSTSEC-2026-0310 json
Various panics, soundness and resource exhaustion issues
published last mo. modified last mo.
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
Version 0.12.3 fixes a large number of panics, soundness issues, and CPU and memory exhaustion issues in all parts of the crate.
The following is a summary of the issues per affected components. For details, please see the [release notes](https://github.com/NLnetLabs/domain/releases/tag/v0.12.3).
## Base
* Limited the number of compression pointers that are followed when parsing a compressed name to 255 to avoid following really long chains. * Limited the length of CNAME chains followed by `Message::canonical_name` to 20. This also fixed an integer overflow in this method when ANCOUNT was`u16::MAX`. * Changed `QuestionSection::answer` to skip over all remaining questions without parsing the QNAMEs to avoid being slowed down by malicious names. * Added length checks when scanning and parsing variable length record data types. This fixes issues with the message builder, which assumes that record data is never too large for placing in a message.
## Stub Resolver
* Fixed possible panics in the resolver’s `FoundHosts::qname` and `FoundHosts::canonical_name`. * Fixed various issues in SRV processing.
## Zonefile parsing
* Fixed soundness issues when reading UTF-8 and an integer overflow when reading unsigned integers. * Fixed a panic when reading empty TXT records.
## Client and server transports, DNSSEC signer and validator
Fixed various panics that could be triggered by malicious incoming DNS messages.
## Zonetree
Fixed various panics and a memory exhaustion issue when updating the zone.
## Acknowledgements
We would like to thank Qifan Zhang, Palo Alto Networks, Antoni (Tony) Jagodka ([@DrVelvetFog](https://github.com/DrVelvetFog)), and [@SebastiaanYN](https://github.com/SebastiaanYN) for reporting issues fixed in this release.
Patch / fix
Is RUSTSEC-2026-0310 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | domain | >=0.0.0-0, <0.12.3 |
0.12.3 |
References
Sources
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.