How severe is CVE-2026-7701?

CVE-2026-7701 has a CVSS 3.x base score of 4.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is none, integrity none, and availability low.

Is CVE-2026-7701 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (31st percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-7701?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2026-7701 have an EU (EUVD) identifier?

Yes. CVE-2026-7701 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-26839.

When was CVE-2026-7701 published?

CVE-2026-7701 was published on 2026-05-03 and last updated on 2026-06-17.

CVE-2026-7701

CVE-2026-7701 is a medium-severity vulnerability with a CVSS 3.x base score of 4.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-404.

Key facts

Severity: Medium (CVSS 3.x base score 4.3)
CVSS v2: 5.0
CVSS v4: 2.1
EPSS exploit prediction: 0% (31st percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-26839
Weakness: CWE-404
Published: 2026-05-03
Last modified: 2026-06-17

Description

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."

Frequently asked questions

What is CVE-2026-7701?: 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."
How severe is CVE-2026-7701?: CVE-2026-7701 has a CVSS 3.x base score of 4.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is none, integrity none, and availability low.
Is CVE-2026-7701 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (31st percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-7701?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-7701 have an EU (EUVD) identifier?: Yes. CVE-2026-7701 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-26839.
When was CVE-2026-7701 published?: CVE-2026-7701 was published on 2026-05-03 and last updated on 2026-06-17.

References

Other CWE-404 vulnerabilities

CVE-2023-24444 — Critical (CVSS 9.8): Jenkins OpenID Plugin 2.4 and earlier does not invalidate the previous session on login.
CVE-2024-31611 — Critical (CVSS 9.1): SeaCMS 12.9 has a file deletion vulnerability via admin_template.php.
CVE-2018-8450 — High (CVSS 8.8): A remote code execution vulnerability exists when Windows Search handles objects in memory, aka "Windows Search Remote…
CVE-2026-11317 — High (CVSS 8.7): A denial of service security issue exists in the affected product. The security issue stems from a fault occurring when…
CVE-2022-25762 — High (CVSS 8.6): If a web application sends a WebSocket message concurrently with the WebSocket connection closing when running on…
CVE-2020-26070 — High (CVSS 8.6): A vulnerability in the ingress packet processing function of Cisco IOS XR Software for Cisco ASR 9000 Series…

Browse all CWE-404 vulnerabilities →