Skip to main content
CVE-2025-68644VulnerabilityPublished Updated

CVE-2025-68644: Yealink RPS · Authentication Bypass by Spoofing

Affects Yealink RPSSource CVE Database V5

0

Not known to be exploited · CVSS 7.4 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
7.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Yealink RPSAffected
  • =0
Fixed in–

AI-suggested

European organizations should immediately verify the version of Yealink RPS in use and ensure it is updated to the version released on or after 2025-06-27 that includes the enhanced authentication mechanism. Since the patch is deployed to all cloud instances, organizations using cloud-hosted RPS should confirm with their service provider that the update has been applied. For on-premises deployments, apply vendor-provided patches without delay. Additionally, restrict network access to RPS management interfaces using network segmentation and firewall rules to limit exposure to trusted IP addresses only. Implement strong monitoring and logging of access to RPS systems to detect any unauthorized attempts. Review and enforce strict access control policies for provisioning systems and credentials. Consider employing multi-factor authentication (MFA) where possible for administrative access to provisioning services. Regularly audit provisioning URLs and device configurations for anomalies that may indicate compromise. Finally, maintain an incident response plan that includes scenarios involving telephony infrastructure compromise.

Description

Yealink RPS before 2025-06-27 allows unauthorized access to information, including AutoP URL addresses. This was fixed by deploying an enhanced authentication mechanism through a security update to all cloud instances.

References

Community reviews

Loading reviews…