Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
MEDIUM severity

GHSA-jhj6-5mh6-4pvf

MEDIUMFix: kitabisa/teler@ec60820

GHSA-jhj6-5mh6-4pvf is a medium-severity (CVSS 5.9) NULL Pointer Dereference vulnerability in ktbs.dev/teler. O3 Security confirms whether GHSA-jhj6-5mh6-4pvf is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Denial-of-Service within Docker container

Also known asCVE-2020-26213GO-2022-0903
Published
May 24, 2021
Updated
Jul 8, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Jul 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐹ktbs.dev/teler

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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.

Specific Go Packages Affected

ktbs.dev/teler/pkg/errors

Patches

Upgrade to the >= 0.0.1 version.

Workarounds

N/A

References

For more information

If you have any questions or comments about this advisory:

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Goktbs.dev/telerall versions0.0.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ktbs.dev/teler. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update ktbs.dev/teler to 0.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jhj6-5mh6-4pvf is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-jhj6-5mh6-4pvf is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-jhj6-5mh6-4pvf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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. ### Specific Go Packages Affected ktbs.dev/teler/pkg/errors ### Patches Upgrade to the >= 0.0.1 version. ### 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](https://github.com/kitabisa/tele
O3 Security · Impact-Aware SCA

Is GHSA-jhj6-5mh6-4pvf in your dependencies?

O3 detects GHSA-jhj6-5mh6-4pvf across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.