limbo.watch

In limbo for 69 days

GHSA-4jwp-xjwm-333g

hickory-recursor on crates.io · published in hickory-dns/hickory-dns

Read the advisory on GitHub ↗

Facts

Severity
Medium
Affected versions (hickory-recursor)
0.25.0-alpha.3 .. 0.26.0-alpha.1As entered by the maintainer. Not reviewed. Scanners can’t read this range. How to fix it
Fixed in (hickory-recursor)
not stated
Affected versions (hickory-resolver)
0.26.0 .. 0.26.1As entered by the maintainer. Not reviewed. Scanners can’t read this range. How to fix it
Fixed in (hickory-resolver)
0.26.2
Affected versions (hickory-proto)
0.26.0 .. 0.26.1As entered by the maintainer. Not reviewed. Scanners can’t read this range. How to fix it
Fixed in (hickory-proto)
0.26.2
Affected versions (hickory-server)
0.25.0-alpha.1 .. 0.26.1As entered by the maintainer. Not reviewed. Scanners can’t read this range. How to fix it
Fixed in (hickory-server)
0.26.2
CVE
None cited by the advisory
GitHub Advisory Database
Not reviewed
OSV.dev
Not present
Other CVEs pointing here
CVE-2026-123603 (published by another CNA)

If you use hickory-recursor 0.25.0-alpha.3 .. 0.26.0-alpha.1

No fixed version is listed yet. Check the advisory for workarounds. Dependabot, npm audit and OSV-Scanner won’t flag this yet.

Timeline

  1. 2026-09-03 21:54 UTC

    Published by the maintainers

    No CVE cited

  2. 2026-11-08 03:50 UTC

    Change recorded

    new CVE from another CNA: CVE-2026-123603

  3. 2026-10-28 07:20 UTC

    First seen by Limbowatch

    not reviewed · not in OSV

  4. Waiting

    Reviewed by GitHub

  5. Waiting

    In OSV; scanners can see it

Machine-readable record: feed/GHSA-4jwp-xjwm-333g.json