VulnerabilityPublished 24 Mar 2026

CVE-2026-4749: albfan miraclecast · NVD-CWE-noinfo NVD-CWE-noinfo

Affects albfan miraclecastSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 1.0 when convenient.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score

6.5Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.0

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

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

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

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 Oct 2026.

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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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

Upgrade albfan/miraclecast and miraclecast to 1.0.

Affected software

Product	Affected	Fixed in
albfanmiraclecast	Affected <1.0	Fixed in–
GitHubalbfan/miraclecast`pkg:github/albfan/miraclecast`Other threats	Affected <1.0	Fixed in 1.0
GitHubmiraclecast`pkg:github/miraclecast`Other threats	Affected <1.0	Fixed in 1.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Network Segmentation: Restrict miraclecast service access to trusted and isolated network segments to prevent unauthorized adjacent network access.
Access Controls: Implement firewall rules or network ACLs to limit connectivity to miraclecast ports only to authorized devices and users.
Service Hardening: Disable miraclecast if not required or restrict its usage to minimal necessary systems.
Monitoring and Logging: Enable detailed logging of miraclecast activity and monitor for unusual access patterns or unauthorized connections.
Update Management: Regularly check for official patches or updates from the miraclecast project and apply them promptly once available.
Use VPN or Secure Tunnels: If remote access to miraclecast is necessary, enforce secure VPN connections to reduce exposure on adjacent networks.
User Awareness: Educate users and administrators about the risks of exposing miraclecast services on untrusted networks.
Incident Response Preparation: Develop response plans for potential data disclosure incidents related to this vulnerability. These measures go beyond generic advice by focusing on network-level controls, service-specific restrictions, and proactive monitoring tailored to the nature of the vulnerability and the product involved.

Description

NVD-CWE-noinfo vulnerability in albfan miraclecast.This issue affects miraclecast: before v1.0.

Impact

The primary impact of CVE-2026-4749 is unauthorized disclosure of sensitive information due to the high confidentiality impact. Organizations using miraclecast in environments where the service is accessible over adjacent networks are at risk of data leakage. Since the vulnerability does not affect integrity or availability, it does not enable attackers to modify data or disrupt services directly. However, the ability to access confidential data without authentication can lead to secondary impacts such as information theft, privacy violations, and potential reconnaissance for further attacks. The medium severity rating reflects the balance between the high confidentiality impact and the requirement for network proximity, which limits remote exploitation. Industries relying on wireless display technologies for presentations, collaboration, or digital signage, especially in sensitive environments like government, healthcare, or finance, could face significant risks if miraclecast is deployed without proper network controls. The absence of known exploits reduces immediate threat but does not eliminate the risk, especially once exploit code becomes available. The lack of patches means organizations must rely on mitigation strategies until an official fix is released.

References

github.com/albfan/miraclecast/pull/555 (opens in a new tab)

Community reviews

Loading reviews…