Which versions of badkeys are affected by CVE-2026-21439?

badkeys (pip) versions <= 0.0.15 is affected.

Is there a fix for CVE-2026-21439?

Yes. CVE-2026-21439 is fixed in 0.0.16. Upgrade to this version or later.

Is CVE-2026-21439 exploitable, and should I be worried?

Whether CVE-2026-21439 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-21439 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-21439?

Upgrade badkeys to 0.0.16 or later.

CVE-2026-21439 in badkeys

Q: What is CVE-2026-21439?

CVE-2026-21439 is a low-severity security vulnerability in badkeys (pip), affecting versions <= 0.0.15. It is fixed in 0.0.16.

Q: Is there a fix for CVE-2026-21439?

Yes. CVE-2026-21439 is fixed in 0.0.16. Upgrade to this version or later.

Q: Is CVE-2026-21439 exploitable, and should I be worried?

Whether CVE-2026-21439 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-21439 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-21439?

Upgrade badkeys to 0.0.16 or later.

CVE-2026-21439

CVE-2026-21439 is a low-severity security vulnerability in badkeys (pip), affecting versions <= 0.0.15. It is fixed in 0.0.16.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

badkeys vulnerable to ASCII control character injection on console via malformed input

Resources

https://github.com/badkeys/badkeys/issues/40

Impact

An attacker may inject content with ASCII control characters like vertical tabs, ANSI escape sequences, etc., that can create misleading output of the badkeys command-line tool. This impacts scanning DKIM keys (both --dkim and --dkim-dns), SSH keys (--ssh-lines mode), and filenames in various modes.

Affected versions

badkeys (<= 0.0.15)

Security releases

badkeys → 0.0.16 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

This has been fixed with the following commits:
https://github.com/badkeys/badkeys/commit/de631f69f040974bb5fb442cdab9a1d904c64087
https://github.com/badkeys/badkeys/commit/635a2f3b1b50a895d8b09ec8629efc06189f349a

All users should upgrade badkeys to version 0.0.16.

Frequently Asked Questions

What is CVE-2026-21439? CVE-2026-21439 is a low-severity security vulnerability in badkeys (pip), affecting versions <= 0.0.15. It is fixed in 0.0.16.
Which versions of badkeys are affected by CVE-2026-21439? badkeys (pip) versions <= 0.0.15 is affected.
Is there a fix for CVE-2026-21439? Yes. CVE-2026-21439 is fixed in 0.0.16. Upgrade to this version or later.
Is CVE-2026-21439 exploitable, and should I be worried? Whether CVE-2026-21439 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-21439 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-21439? Upgrade badkeys to 0.0.16 or later.