Skip to main content
Mallory
UnratedVulnerability

CVE-2026-19720: Buffer Overflow in GNU Inetutils talkd via Long DNS Names

Updated 3 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-19720CWE-120

CVE-2026-19720 is a buffer overflow vulnerability in GNU Inetutils talkd triggered by excessively long DNS names. Available information indicates that the flaw occurs during handling of DNS-derived host name data within talkd, where insufficient bounds checking allows an overlong name to overflow a buffer. The issue was reproduced by the maintainer, patched, and validated during coordinated disclosure. Specific vulnerable function details are not currently available.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation may cause process memory corruption in talkd, leading to denial of service through a crash. Depending on the surrounding memory layout, compiler protections, and runtime conditions, buffer overflow conditions of this type can potentially be leveraged for arbitrary code execution, but the currently available information does not confirm code execution in this case.

Mitigation

If you can’t patch tonight, do this now.

Until patched versions are deployed, reduce exposure by disabling talkd if it is not required, restricting network access to the service to trusted hosts and networks, and limiting use in environments where untrusted or attacker-controlled name resolution data can reach the daemon. Additional hardening such as compiler and runtime memory protections may reduce exploit reliability but does not eliminate the underlying flaw.

Remediation

Patch, then assume compromise.

Upgrade GNU Inetutils to a version containing the vendor patch for CVE-2026-19720. Apply the maintainer-provided fix that adds proper bounds checking or otherwise safely handles long DNS names in talkd. If distribution packages are used, install the corresponding security update from the operating system vendor once available.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-19720 exploited in the wild?
As of Nov 19, 2026, Mallory has no reports of CVE-2026-19720 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-19720?
As of Nov 19, 2026, Mallory has found no public exploit for CVE-2026-19720.
Is there a patch for CVE-2026-19720?
Upgrade GNU Inetutils to a version containing the vendor patch for CVE-2026-19720. Apply the maintainer-provided fix that adds proper bounds checking or otherwise safely handles long DNS names in talkd.
Activity feed

Recent activity

4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity3Community discussion across Reddit, Mastodon, and other social sources.