dbcve.org
TelegramApplication

CVE-2020-10570

MEDIUM · 6.1 CVSS v3.1 Published 2020-03-24
Fix available
A fix is available. Upgrade to after 5.12.0 or later.
See remediation →
66/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Telegram application through 5.12 for Android, when Show Popup is enabled, might allow physically proximate attackers to bypass intended restrictions on message reading and message replying. This might be interpreted as a bypass of the passcode feature.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Telegram Android app versions through 5.12 have a vulnerability where the 'Show Popup' notification feature, when enabled, can be exploited by physically proximate attackers to bypass the passcode lock and read or reply to messages without authentication.

MitigationUsers should disable the 'Show Popup' notification feature in Telegram settings as a workaround until a vendor patch is available; organizations should verify current Telegram versions in use and enforce updated versions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TelegramApplication
Affected:<= 5.12.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Physical
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Telegram Android is installed
    Check the device's installed applications for the Telegram app (package name: org.telegram.messenger or org.telegram.messengerbeta)
    Affected if Telegram Android app is present on the device
  2. Check Telegram Android version
    Open Telegram, go to Settings > About (or Settings > Help > About) to view the installed version number
    Affected if Installed version is 5.12.0 or lower (any version through 5.12)
  3. Confirm Show Popup notification feature is enabled
    In Telegram, navigate to Settings > Notifications and Sounds > Popup notification, or Settings > Privacy and Security > Notifications > Show popup, and verify the feature is turned ON
    Affected if Show Popup notification is enabled in Telegram settings

A user is affected if they have Telegram Android version 5.12.0 or lower with the Show Popup notification feature enabled, as this combination allows the passcode lock bypass to succeed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 5.12.0
Interim mitigation

Users should disable the 'Show Popup' notification feature in Telegram settings as a workaround until a vendor patch is available; organizations should verify current Telegram versions in use and enforce updated versions.

Fix this in Telegram Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-10570 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-10570 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data