Skip to main content
VulnerabilityPublished Updated

CVE-2026-27831: bluedragonsecurity rldns · Out-of-bounds Read

Affects bluedragonsecurity rldnsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High · fixed in 1.4 : patch bluedragonsecurity rldns soon.

Data as of 31 Oct 2026, 08:20 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
bluedragonsecurityrldnsAffected
  • =1.3
Fixed in–
GitHubbluedragonsecurity/rldnspkg:github/bluedragonsecurity/rldnsOther threatsAffected
  • =1.3
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately upgrade rldns installations from version 1.3 to version 1.4 or later, where the vulnerability has been patched. If upgrading is not immediately feasible, network-level mitigations such as restricting access to the DNS server to trusted IP addresses and implementing rate limiting on DNS queries can reduce exposure. Monitoring DNS server logs for abnormal crashes or unusual query patterns may help detect attempted exploitation. Employing intrusion detection systems (IDS) with signatures for anomalous DNS traffic can provide early warnings. Additionally, organizations should conduct an inventory of DNS servers to identify any running vulnerable versions of rldns and prioritize patching those exposed to untrusted networks. Regularly updating and applying security patches to DNS infrastructure is critical to maintaining availability and resilience against denial of service attacks.

Description

rldns is an open source DNS server. Version 1.3 has a heap-based out-of-bounds read that leads to denial of service. Version 1.4 contains a patch for the issue.

References

Community reviews

Loading reviews…