CVE-2026-1735VulnerabilityPublished 2 Feb 2026Updated 23 Feb 2026

CVE-2026-1735: Yealink MeetingBar A30 · Command Injection

Affects Yealink MeetingBar A30Source CVE Database V5

Not known to be exploited · CVSS 2.4 Low.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

2.4Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 1.3% chance of exploitation in 30 days – higher than 71% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Physical
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable system. Physical interaction may be brief (e.g., evil maid attack) or persistent.
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
YealinkMeetingBar A30	Affected =133.321.0.3	Fixed in–

AI-suggested

1. Enforce strict physical security controls around Yealink MeetingBar A30 devices to prevent unauthorized physical access, including locked rooms and restricted access policies. 2. Implement network segmentation to isolate MeetingBar devices from critical network segments, limiting potential lateral movement if compromised. 3. Monitor device logs and network traffic for unusual activity indicative of command injection or unauthorized access attempts. 4. Disable or restrict access to the Diagnostic Handler component if possible, or limit its usage to trusted personnel only. 5. Maintain an inventory of all Yealink MeetingBar A30 devices and their firmware versions to identify affected units. 6. Engage with Yealink support channels regularly to obtain updates or patches addressing this vulnerability. 7. Consider deploying additional endpoint detection and response (EDR) solutions on networks where these devices operate to detect anomalous behavior. 8. Educate staff about the risks of physical device tampering and encourage reporting of suspicious activity. 9. If feasible, replace affected devices with models not vulnerable or with vendor-supported patches once available.

Description

A weakness has been identified in Yealink MeetingBar A30 133.321.0.3. This issue affects some unknown processing of the component Diagnostic Handler. This manipulation causes command injection. It is feasible to perform the attack on the physical device. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The primary impact of this vulnerability is on the integrity and availability of the Yealink MeetingBar A30 device. Successful exploitation could allow an attacker to execute arbitrary commands on the device, potentially leading to device malfunction, unauthorized configuration changes, or disruption of video conferencing services. While confidentiality impact is limited due to physical access requirements, compromised devices in sensitive environments could be leveraged for further lateral movement or espionage. Organizations relying heavily on Yealink MeetingBar A30 for critical communications may experience operational disruptions. The public release of exploit code increases the likelihood of insider threats or attackers with physical access exploiting this vulnerability. The absence of a vendor patch prolongs exposure and complicates remediation efforts. Overall, the threat is moderate for organizations with physical security gaps around these devices but low for those with strict physical access controls.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 21:54 UTC

Technical details

References

Community reviews

Related threats