{"answers":{"affected":"1 open source package ship an affected version, including domain.","exploited":"There is no known exploitation of RUSTSEC-2026-0310 in the wild and no public exploit code.","fix":"Upgrade domain to 0.12.3 or later.","what":"RUSTSEC-2026-0310 is a denial of service vulnerability in domain, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0310 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0310 is a denial of service vulnerability in domain, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of RUSTSEC-2026-0310 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- domain (crates.io): affected from 0.0.0-0; fixed in 0.12.3\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/RUSTSEC-2026-0310/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0310/index.md)","id":"RUSTSEC-2026-0310","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0310/index.md","name":"RUSTSEC-2026-0310","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust DNS library","requires_auth":"none","summary":"Attackers can cause denial of service via resource exhaustion or panics by sending malicious DNS messages to applications using this Rust DNS library.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"Version 0.12.3 fixes a large number of panics, soundness issues, and\nCPU and memory exhaustion issues in all parts of the crate.\n\nThe following is a summary of the issues per affected components.\nFor details, please see the [release\nnotes](https://github.com/NLnetLabs/domain/releases/tag/v0.12.3).\n\n## Base\n\n* Limited the number of compression pointers that are followed when parsing\n  a compressed name to 255 to avoid following really long chains.\n* Limited the length of CNAME chains followed by `Message::canonical_name`\n  to 20. This also fixed an integer overflow in this method when ANCOUNT\n  was`u16::MAX`.\n* Changed `QuestionSection::answer` to skip over all remaining questions\n  without parsing the QNAMEs to avoid being slowed down by malicious\n  names.\n* Added length checks when scanning and parsing variable length record\n  data types. This fixes issues with the message builder, which assumes that\n  record data is never too large for placing in a message.\n\n## Stub Resolver\n\n* Fixed possible panics in the resolver’s `FoundHosts::qname` and\n  `FoundHosts::canonical_name`.\n* Fixed various issues in SRV processing.\n\n## Zonefile parsing\n\n* Fixed soundness issues when reading UTF-8 and an integer overflow when\n  reading unsigned integers.\n* Fixed a panic when reading empty TXT records.\n\n## Client and server transports, DNSSEC signer and validator\n\nFixed various panics that could be triggered by malicious incoming DNS\nmessages.\n\n## Zonetree\n\nFixed various panics and a memory exhaustion issue when updating the zone.\n\n## Acknowledgements\n\nWe would like to thank Qifan Zhang, Palo Alto Networks,\nAntoni (Tony) Jagodka ([@DrVelvetFog](https://github.com/DrVelvetFog)),\nand [@SebastiaanYN](https://github.com/SebastiaanYN) for\nreporting issues fixed in this release.","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Various panics, soundness and resource exhaustion issues","id":"RUSTSEC-2026-0310","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.12.3"],"introduced":["0.0.0-0"],"last_affected":[],"package":"domain","purl":"pkg:cargo/domain","source":"RUSTSEC-2026-0310"}],"products":null,"published":"2026-09-25","related":[],"sources":[{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can cause denial of service via resource exhaustion or panics by sending malicious DNS messages to applications using this Rust DNS library.","url":"https://insights.sbomify.com/RUSTSEC-2026-0310/"}