CVE-2026-7701

MEDIUMNVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

Score 4.3 from GitHub Security Advisory (severity: LOW) published 2026-05-03. NVD baseline CVSS 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
4.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A security vulnerability has been detected in Telegram Desktop up to 6.7.5. This vulnerability affects the function RequestButton of the file Telegram/SourceFiles/boxes/url_auth_box.cpp of the component Bot API. The manipulation of the argument login_url leads to null pointer dereference. It is possible to initiate the attack remotely. The exploit has been disclosed publicly and may be used. There is ongoing doubt regarding the real existence of this vulnerability. Upgrading to version 6.7.6 is able to resolve this issue. Upgrading the affected component is recommended. The vendor provides this rationale for the dispute: "[T]he described scenario does not lead to any security issue or vulnerability, and only causes a one-time crash. In the outlined scenario, the targeted user must perform an active action, which doesn't produce any consequences after the app is relaunched."

CVSS v3
4.3
EG Score
4.3(medium)
EPSS
31.7%
KEV
Not listed

Published

May 3, 2026

Last Modified

May 19, 2026

Advisory Details (1)

Auto-updated May 3, 2026
No patch confirmed yet.
generic
https://www.youtube.com/watch?v=xo9Bplsy1K8

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-16 17:03 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 02:00 UTCEPSS rescore
  4. 2026-07-13 22:31 UTCEPSS rescore
  5. 2026-07-13 06:13 UTCEPSS rescore
  6. 2026-07-12 05:46 UTCEPSS rescore
  7. 2026-07-11 08:27 UTCEPSS rescore
  8. 2026-07-09 19:10 UTCEPSS rescore
  9. 2026-07-09 19:10 UTCEPSS rescore
  10. 2026-07-08 15:16 UTCEPSS rescore
  11. 2026-07-08 15:16 UTCEPSS rescore
  12. 2026-07-07 13:46 UTCEPSS rescore
  13. 2026-07-07 13:46 UTCEPSS rescore
  14. 2026-07-06 16:27 UTCEPSS rescore
  15. 2026-07-06 16:27 UTCEPSS rescore
  16. 2026-07-06 02:23 UTCEPSS rescore
  17. 2026-07-06 02:23 UTCEPSS rescore
  18. 2026-07-05 02:31 UTCEPSS rescore
  19. 2026-07-05 02:30 UTCEPSS rescore
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-04 06:31 UTCEPSS rescore
  22. 2026-07-01 15:07 UTCEPSS rescore
  23. 2026-06-30 23:22 UTCEPSS rescore
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-28 14:07 UTCEPSS rescore
Show 54 more
  1. 2026-06-28 04:56 UTCEPSS rescore
  2. 2026-06-27 03:08 UTCEPSS rescore
  3. 2026-06-25 13:50 UTCEPSS rescore
  4. 2026-06-24 14:05 UTCEPSS rescore
  5. 2026-06-23 21:33 UTCEPSS rescore
  6. 2026-06-22 14:25 UTCEPSS rescore
  7. 2026-06-21 14:56 UTCEPSS rescore
  8. 2026-06-21 01:59 UTCEPSS rescore
  9. 2026-06-19 19:26 UTCEPSS rescore
  10. 2026-06-18 17:52 UTCEPSS rescore
  11. 2026-06-17 17:53 UTCEPSS rescore
  12. 2026-06-16 17:53 UTCEPSS rescore
  13. 2026-06-15 17:49 UTCEPSS rescore
  14. 2026-06-15 17:49 UTCEPSS rescore
  15. 2026-06-14 23:18 UTCEPSS rescore
  16. 2026-06-14 08:23 UTCGHSA enrichment
  17. 2026-06-13 23:00 UTCEPSS rescore
  18. 2026-06-12 23:12 UTCEPSS rescore
  19. 2026-06-12 23:12 UTCEPSS rescore
  20. 2026-06-12 04:55 UTCGHSA enrichment
  21. 2026-06-11 14:00 UTCEPSS rescore
  22. 2026-06-11 03:05 UTCGHSA enrichment
  23. 2026-06-10 22:19 UTCEPSS rescore
  24. 2026-06-10 13:22 UTCEPSS rescore
  25. 2026-06-10 00:53 UTCGHSA enrichment
  26. 2026-06-08 23:04 UTCGHSA enrichment
  27. 2026-06-08 14:17 UTCEPSS rescore
  28. 2026-06-07 21:14 UTCGHSA enrichment
  29. 2026-06-07 15:25 UTCEPSS rescore
  30. 2026-06-06 19:24 UTCGHSA enrichment
  31. 2026-06-06 13:47 UTCEPSS rescore
  32. 2026-06-05 22:47 UTCEPSS rescore
  33. 2026-06-05 17:33 UTCGHSA enrichment
  34. 2026-06-05 06:10 UTCEPSS rescore
  35. 2026-06-04 15:39 UTCGHSA enrichment
  36. 2026-06-04 13:12 UTCEPSS rescore
  37. 2026-06-03 13:49 UTCGHSA enrichment
  38. 2026-06-02 20:13 UTCEPSS rescore
  39. 2026-06-02 11:59 UTCGHSA enrichment
  40. 2026-06-01 13:52 UTCEPSS rescore
  41. 2026-06-01 10:09 UTCGHSA enrichment
  42. 2026-05-31 22:30 UTCEPSS rescore
  43. 2026-05-31 00:16 UTCEPSS rescore
  44. 2026-05-29 13:44 UTCEPSS rescore
  45. 2026-05-28 13:44 UTCEPSS rescore
  46. 2026-05-27 13:40 UTCEPSS rescore
  47. 2026-05-27 13:40 UTCEPSS rescore
  48. 2026-05-26 13:44 UTCEPSS rescore
  49. 2026-05-26 07:18 UTCEPSS rescore
  50. 2026-05-21 22:43 UTCEPSS rescore
  51. 2026-05-20 22:38 UTCEPSS rescore
  52. 2026-05-20 14:42 UTCEG score recompute
  53. 2026-05-20 14:42 UTCGHSA enrichment
  54. 2026-05-20 11:22 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-7701?
CVE-2026-7701 is a medium vulnerability published on May 3, 2026. A security vulnerability has been detected in Telegram Desktop up to 6.7.5. This vulnerability affects the function RequestButton of the file Telegram/SourceFiles/boxes/urlauthbox.cpp of the component Bot API. The manipulation of the argument login_url leads to null pointer dereference. It is…
When was CVE-2026-7701 disclosed?
CVE-2026-7701 was first published in the National Vulnerability Database on May 3, 2026, with the most recent update on May 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-7701 actively exploited?
CVE-2026-7701 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 31.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-7701?
CVE-2026-7701 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-7701?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-7701, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-7701

Explore →

Is Your Infrastructure Affected by CVE-2026-7701?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs