What is CVE-2020-26213?

CVE-2020-26213 is a medium-severity null pointer dereference vulnerability in ktbs.dev/teler (go), affecting versions < 0.0.1. It is fixed in 0.0.1. The application dereferences a null pointer, causing a crash.

How severe is CVE-2020-26213?

CVE-2020-26213 has a CVSS score of 5.9 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of ktbs.dev/teler are affected by CVE-2020-26213?

ktbs.dev/teler (go) versions < 0.0.1 is affected.

Is there a fix for CVE-2020-26213?

Yes. CVE-2020-26213 is fixed in 0.0.1. Upgrade to this version or later.

Is CVE-2020-26213 exploitable, and should I be worried?

Whether CVE-2020-26213 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-2020-26213 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-2020-26213?

Upgrade ktbs.dev/teler to 0.0.1 or later.

CVE-2020-26213 in ktbs.dev/teler

Q: How severe is CVE-2020-26213?

CVE-2020-26213 has a CVSS score of 5.9 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of ktbs.dev/teler are affected by CVE-2020-26213?

ktbs.dev/teler (go) versions < 0.0.1 is affected.

Q: Is there a fix for CVE-2020-26213?

Yes. CVE-2020-26213 is fixed in 0.0.1. Upgrade to this version or later.

Q: Is CVE-2020-26213 exploitable, and should I be worried?

Whether CVE-2020-26213 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-2020-26213 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-2020-26213?

Upgrade ktbs.dev/teler to 0.0.1 or later.

Summary

Denial-of-Service within Docker container

Specific Go Packages Affected

ktbs.dev/teler/pkg/errors

Workarounds

N/A

References

https://github.com/kitabisa/teler/commit/ec6082049dba9e44a21f35fb7b123d42ce1a1a7e

For more information

If you have any questions or comments about this advisory:

Open an issue in Issues Section
Email us at [email protected]

Impact

If you run teler inside a Docker container and encounter errors.Exit function, it will cause denial-of-service (SIGSEGV) because it doesn't get process ID and process group ID of teler properly to kills.

The application dereferences a null pointer, causing a crash. Typical impact: denial of service via crash.

CVE-2020-26213 has a CVSS score of 5.9 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.0.1); upgrading removes the vulnerable code path.

Affected versions

ktbs.dev/teler (< 0.0.1)

Security releases

ktbs.dev/teler → 0.0.1 (go)

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

Upgrade to the >= 0.0.1 version.

Frequently Asked Questions

What is CVE-2020-26213? CVE-2020-26213 is a medium-severity null pointer dereference vulnerability in ktbs.dev/teler (go), affecting versions < 0.0.1. It is fixed in 0.0.1. The application dereferences a null pointer, causing a crash.
How severe is CVE-2020-26213? CVE-2020-26213 has a CVSS score of 5.9 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of ktbs.dev/teler are affected by CVE-2020-26213? ktbs.dev/teler (go) versions < 0.0.1 is affected.
Is there a fix for CVE-2020-26213? Yes. CVE-2020-26213 is fixed in 0.0.1. Upgrade to this version or later.
Is CVE-2020-26213 exploitable, and should I be worried? Whether CVE-2020-26213 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-2020-26213 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-2020-26213? Upgrade ktbs.dev/teler to 0.0.1 or later.