- Exploited
- No known exploitation
- Fix
- Fixed in 0.26.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.26.2.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 16/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach16/20hickory-proto: 2.6M downloads a week
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 38 if advisories confirm default setups are exposed
Impact
- Widely used
hickory-proto has 2.6m weekly downloads.Source: crates.io
What to do
Upgrade to a fixed version: 0.26.2.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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"}.Timeline
- Advisory published69 days
- Record last updated
Affected versions
- hickory-protocrates.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.
Evidence 3
Other links · 3
- Advisory
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about RUSTSEC-2026-0489
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: cve.now feed data
Which versions are affected by RUSTSEC-2026-0489?
hickory-proto (crates.io): from 0.20.1 before 0.26.2.Source: cve.now feed data
How do I fix RUSTSEC-2026-0489?
Upgrade to a fixed version: 0.26.2.Source: cve.now feed data