RUSTSEC-2026-0310: Various panics, soundness and resource exhaustion issues
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Fixed version: domain (crates.io) 0.12.3.
Low priority for now. Upgrade to domain (crates.io) 0.12.3 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: OSV
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.
- Published
- Sep 25, 2026
- Updated
- Sep 25, 2026
- EPSS
- —
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
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.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| crates.io | domain | pkg:cargo/domain |
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| crates.io | domain | from 0.0.0-0 · before 0.12.3 | 0.12.3 |
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| crates.io:domain | 0.12.3 | Package 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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.